SCCM 2012 R2 Step by Step Guide Welcome to System Center 2012 R2 Configuration Manager step by step guide,SCCM 2012 R2 Step by Step Guide. Deploy Adobe Reader Updates Sccm 2012 FspSCCM 2. R2 Step by Step Guide. Prajwal,Have you seen this problem CAS cant access SMSCAS SMSSITEI have an open case with Microsoft SCCM 2. My environment in test its been up running for 2 months at least Server 2. R2 Standard SCCM 2. R2 CU1 SQL 2. 01. Standard SP1 1 CAS 1 x Primary Remote SQL either on CAS or Primary. From CAS, log in as SCCM Admin Service Account as Domain Admins, SCCM Admin Service Account cant access SMSCAS SMSSITEMessage Windows cannot access sccmcas. SMSCASYou do not have permission to access sccmcas. SMSCAS. Contact your network administrator to request access. Windows cannot access sccmcas. SMSSITEYou do not have permission to access sccmcas. I want to update third party software such as adobe reader any help pleaseSMSSITE. Contact your network administrator to request access. BUT from Primary Site theres no problem accesssccmcas. Deploy Adobe Reader Updates Sccm 2012' title='Deploy Adobe Reader Updates Sccm 2012' />Deploy Adobe Reader Updates Sccm 2012 DiscoverySMSCASsccmcas. SMSSITEAnd I just stood up my production 3 days ago, havent deploy the SCCM client yet just finished setting up boundaries, AD discovery, etc. The same problem occurs as well. Did I miss something here OR new undiscovered bugs either in Windows Server 2. R2 or SCCM 2. 01. R2. I really appreciated any help on this. Its been one week. How to deploy Software using Group Policy. Originally this was just going to be a post showing you how to deploy the Windows In. Tune client to a computer using Group Policy however it turned out I think this article would be best suited to show you how to use some advanced techniques to deploy software via Group Policy. So even if you dont want to specifically  deploy the In. Tune software client to your computers this article will still serve you as a good reference for Group Policy software deployment in general. Tip 1 DONT If at all possible do not deploy software this way Group Policy software deployment has a number of restrictions that makes this one of the less desirable methods of software deployment. Some of the reasons why I would not recommend this deployment method are Lack or scheduling. When you deploy software to a computer using Group Policy it will only ever installun install on the next reboot of the computer. This makes it very difficult to schedule rollouts especially when deploying large software updates that would put immense load on the LAN when deploying to all the computers first thing in the morning when they are all turned on at the same time. Using something like SCCM is much better with it options for maintenance windows and Wake On LAN optionsMSI and ZAP Installer Only. The only supported applications formats are the more popular MSI installer and the lesser known ZAP package format. This is somewhat restrictive and again software deployment tools like SCCM are vasty superior as they support any sort of installation method. Fixed Application Install Order. When you add application to the Group Policy Object they install onto the computer in the same order with no way of changing this order. Nill Visibility. When you go to deploy software using Group Policy the configuration it pushed to the computers but there is never any feedback on weather the software has successfully installed. This lack of visibility could mean you think you have deployed something to all your computers successfully but in reality it has failed to install on many of the computers. Poor Scoping. When you deploy software using Group Policy you can only specify a UNC path as the location to install the software from. If you have specified a single server in head office this would mean that all the workstation at remote sites will try and download and install over the WAN Not good. I will make a few recommendation further on as to how to mitigate this however other deployment software tools again like SCCM handle this much more automatically which can reduce you admin overhead. Now that I have sufficiently warned you about Group Policy Software Deployment I would also say there is one exception to this rule where and that is Agent software Deployment. Weather it is SCCM Agent or In. Microsoft Sql Server Login Connection Failed Sqlstate 08001 Sql. Tune or even a Anit Virus software package GP Software deployment is good at deploying the same software package to a large number of computers. And speaking of services that require agentsWindows In. Tune is a new services that is offered by Microsoft that allows IT administrators to manage and monitor computers via a web based console. This service has been often referred to as SCCM in the cloud as it allows you to manage many workstations without the need for any server infrastructure. For more information on Windows In. Tune visit http www. While there is no software to install on servers for the In. Tune to work it does require you deploy a management client to your workstations. This client software can be either installed manually but when you have 1. Microsoft also provides a way to deploy the In. Tune client via Group Policy. Configuring the application install files for Group Policy Deployment. Step 1 Go to Windows Intune website and download the In. Tune Client software. Step 2 Right click on WindowsIntuneSetup. Extract All option. Step 3 Extract the contents of the WindowsIntuneSetup. WindowsIntuneSetup. Step 4 Copy the all the files see below to the software distribution file share in your organisation. WindowsIntuneSetup. WindowsIntuneX6. WindowsIntuneX8. Windows. Intune. accountcert. You have now setup the installation files for the In. Tune client or other software ready to be deployed in your organisation. Tip 2 This location needs to have read permission for the Domain Computers group applied so that the computer can download and install the files.