How To Install Sccm Agent

During an installation and fractional upgrade of SCCM clients on my work we ran into som issues. About 200 clients was unable to be installed with the client push method. The log on the server didn't get me whatever wiser then something else had to be washed.

I came across Jason Sandys logon script and tested it out. Unfortunately the logon script was only ran on cable connections, due to slow network authentication on wireless adapters resulted in skipping the step.

Therefore i decided to employ a Scheduled task instead.
This setup has been implemented on my own dev setup and has been implemented at my workplace with dandy effect.
I recommend reading the documentation of Jasons script before implementing this setup.

What y'all need:

• Share with read acces for Domain Computers containing the client installation files.
• Share with total control for Domain Computers for error logging.
• GPO creating folders, and copying Jasons script to the client.
• GPO creating a scheduled task running the script in System context.

Step one – Creating the shares

Make 2 shares on a server that are reachable for the clients.The offset share are for the SCCM Agent Cleint setup files.Get to the Sharing pane and click on Advanced Sharing a give the folder a share name.

I cull to call mine SCCMAgentFiles.

Give everyone total control on the share permissions as the security rights will overrule this. When it comes to share/security permissions, information technology'southward always the well-nigh restrictive that wins.

Make sure Authenticated users are removed from the security rights and that it's but Information technology personal that have full control of the folder along with Domain Computers that take read access.

Move the client files to the binder:

The 2nd share are for the Jason scipt fault log, which is only used if something goes wrong in the installation on the client. Follow the same steps as the other share merely give the Domain Computers Full Control instead of read, as the clients needs to write the log, and delete it if the installation succeeds on a later run. This share is chosen ErrorLog.

Step 2 – Configure the ConfigMgrStartup.xml file to your needs

Here is how i configured the XML. MinimumInterval and Filibuster has been configured with 0 as its managed by the scheduled chore.

[code language="xml"] <?xml version="1.0"?> <Startup> 	<Choice Proper noun="SiteCode" >S01</Selection> 	<Pick Name="CacheSize">8120</Option> 	<Option Name="AgentVersion">v.00.8498.1711</Pick> 	<Option Proper name="MinimumInterval">0</Pick> 	<Option Name="ClientLocation">\\WIN-85I5DCAJ027\SCCMAgentFiles</Option> 	<Option Name="MaxLogFile">2048</Option> 	<Option Name="ErrorLocation">\\WIN-85I5DCAJ027\ErrorLog</Selection> 	<Option Proper name="Delay">0</Option> 	<InstallProperty Proper name="SMSMP">SCCM2016.ad.mutsdomain</InstallProperty> 	<InstallProperty Proper name="SMSSLP">SCCM2016.ad.mutsdomain</InstallProperty> 	<CCMSetupParameter Name="BITSPriority">High</CCMSetupParameter> 	<CCMSetupParameter Proper name="noservice" /> </Startup>  [/lawmaking]

Read Jasons documentation for further XML configuration options.

After the XML has been configured, re-create the files to a share where all clients have access. I used the SYSVOL folder on the domain controller as this folder is already readable for the Authenticated Users.

Step iii – Configuring the GPO(south)

Last step is to configure GPO(due south) and so that the folders and script files are copied to the client. I have chosen to configure it all in one GPO that's linked to all workstations.

First go to the folder policies for the Calculator Configuration.

Make the folder structure in the correct order. I have used the C:\Windows\CustomScripts\SCCM\AgentInstall folder for the scripts. And to just apply one time.

Become to the files section.

Brand an entry that copy all the files from the share to the folder you created.

Source file(s):\\Win-85i5dcaj027\netlogon\SCCM\AgentInstall\*
Destination folder:C:\Windows\CustomScripts\SCCM\AgentInstall

Also hither i but apply it in one case.

Configure the scheduled task.

Create a new Scheduled task(At least Windows 7) with the following configuration. Make it run every bit SYSTEM and set information technology to update every bit that volition update settings if you make changes on a later time.

Configure the triggers. I cull to make the script run once every hour as information technology's very simple and has no performance impact what so e'er.

Brand the activeness. The action is the script execution and here it's very important that you utilize the full path in the parameter, otherwise the script will non be able to locate the XML file.

Script: C:\Windows\CustomScripts\SCCM\AgentInstall\ConfigMgrStartup1.75.vbs
Arguments:/Config:C:\Windows\CustomScripts\SCCM\AgentInstall\ConfigMgrStartup.xml

Set the schedule to only run if there is a network connexion available. If the script runs and the client can't admission the shares, the script will then exit.

In the settings pane, make sure that the schedule can exist startet on demand and dual instances is not possible.

That'southward information technology! Do a gpupdate on the client and see if the folders/files are created and that the scheduled chore is created and set to run within an 60 minutes.

We managed to migrate/install 180 clients with a 96% success rate with this setup.

Feel free to leave a comment!

Source: https://www.mroenborg.com/sccm-agent-installation-how-to-implement-jason-sandys-script-as-an-scheduled-task/

Posted by: munztamed1976.blogspot.com

Share this post