Recently completed an R2 upgrade of a Primary Site with multiple Secondary Sites, as expected this was ‘interesting.’ I’ve captured our experiences below – hopefully this will be useful for someone else about to go through a similar excerise.
We’re currently testing a Windows 2012 R2 DirectAccess deployment, part of this is includes a swathe of application testing. During this testing we found that SCCM clients were unable to download content from any DPs, meaning Software Deployment was failing when connected via DirectAccess. The solution is not suprising – you need to modify the SCCM Boundaries and ensure you have defined a boundary for your IPv6 Prefix, assigned to your DirectAccess clients.
To find the prefix, view the properties of a DirectAccess-enabled device in SCCM – you’ll see the detected IPv6 prefixes within the captured properties. Simply add the correct prefix to your SCCM boundary configuration.
This has been a personal bugbear of mine for a while – if DPI settings on a client device are set to 125% or even 150% the SCCM Application Catalog is terrible, requiring users to scroll in virtually every direction to use the website.
I came across the following MS connect post today that offers a temporary workaround.
Modify the Main.css file located under: <SCCM install directory>\SMS_CCM\CMApplicationCatalog\Content\Main.css, change the #ASPcontainer element to look as follows:
#ASPcontainer
{
position: fixed;
height: 99.5%;
width: 100%;
}
This will not survive re-installation of the AppCat role, nor will it survivce AppCat upgrades. Change requires no restart/iisreset – effective immediately.
So we have some SharePoint 2010 Photo Libraries that users want to bulk-upload photos to, these users however are running Office 2013 which means they do not have the “Microsoft Office Picture Manager” utility – in fact this was depreciated with Office 2013.
Rather than deploying an Office 2010 application specifically for this purpose we simply advised the user to map a network drive to the Picture Library – just as you would a normal drive, however specify the HTTP/HTTPS path to the library itself, i.e. https://intranet.domain.local/photos – users can then drag and drop as many files as they want.