Skip to main content

SCCM Task Sequence with automated AD Computer naming Web Services


Maik Koster created a wonderful Deployment Web Service which can help an admin automate many AD, SCCM, and MDT tasks within a Task Sequence.  This blog entry is specifically around producing a Computer Name in Active directory and passing this staged computer name into the OSDComputerName TS variable.

1 Download the DWS from here and extract to a directory on your webserver
2 Open IIS Manager and expand Sites.
3 Right click on Default Web Site and choose Add Application
4 Specify an Alias and point the physical path to the extracted directory.
5 Right Click the applications Pools and choose "Add Application Pool"
6 Provide an Application Pool Name
7 Click on Application Pools
8 Right click on your Application Pool and select Advanced Settings
9 In the Process Model area click into the Identity field and then click on the ... Button
10 Choose Custom account and click on Set...
11 Enter a valid Username and Password and click OK
12 Expand Default Web Site and select the new Application created in step 3
13 Right click and choose Manage Application - Advance settings
14 In the General Area > Application Pool field select the Application Pool name created in step 6
15 Expand Default Web Site, Click the Application added in step 4 
16 Click Application Settings on the right and specify the appropriate accounts. See "Configure Application Settings" section below.


CustomSettings.ini Example

[GenerateComputerName]
WebService=http://localhost/WebService/ad.asmx/GenerateComputerName
ComputerNamePrefix=Prefix
CustomUUID=netbootGUID
MachineObjectOU=OUPath
Parameters=Prefix,netbootGUID,OUPath

Configure Application Settings:

On default, the webservice will use the configured application pool user for authentication. It requires only a couple Application Settings to be set:
RootServer - The SCCM Root Server
SLPServer - One SCCM Server with the SLP Role
RootSiteCode - The Root site code

For Access to the MDT Database you need to configure at least
MDTDBServer - The MDT Database server (with Instance if necessary)
MDTDBName - The MDT Database name
MDTDBIntegratedSecurity - Set to "True" if you want to use the application pool account for authentication. If set to "False" you need to supply the following two settings
MDTDBUser - Username to access the MDT Database
MDTDBPassword - Password to access the MDT Database

For Active Directory access, you can optionally configure the following Application Settings. This is only necessary, if the application pool user account does not have enough permissions to do execute the required functions, and/or if you need to access a different domain as the application pool User is member of:
ADDomain - Domain to query (use either "domain.com" or "DC=Domain,DC=COM" format)
ADUsername - Username for authentication
ADPassword - Password for authentication



URLS
Deployment Web service (v7.3)

http://mdtcustomizations.codeplex.com/wikipage?title=Installation%20Guide&referringTitle=Documentation

http://myitforum.com/myitforumwp/2013/03/07/a-quickstart-guide-to-using-web-services-in-mdt-sccm/

ZTI_ExecuteWebService.wsf
http://mdtcustomizations.codeplex.com/releases/view/37245

Comments

  1. Hi,
    The webservice is creating a computerobject that is disabled and OSD cannot join the computer to the domain. How do you solve this?

    ReplyDelete
  2. Hi,
    The webservice is creating a computerobject that is disabled and OSD cannot join the computer to the domain. How do you solve this?

    ReplyDelete
  3. This comment has been removed by a blog administrator.

    ReplyDelete

Post a Comment

Popular posts from this blog

SCCM Unknown computer not able to see Task Sequences after installing Current Branch 1702

Soon after installing SCCM CB 1702 we were unable to see Task Sequences deployed to the unknown collection. This issue was identified as a random system taking the GUID of the 'x64 Unknown Computer (x64 Unknown Computer)' record. As a result it was now a known GUID; as we were only deploying Task Sequences to the Unknown collection none were made available. 'x64 Unknown Computer (x64 Unknown Computer)' record 'x86 Unknown Computer (x86 Unknown Computer)' record To get the GUID of your unknown systems open SQL management studio and run the following command: --Sql Command to list the name and GUID for UnknownSystems record data select ItemKey, Name0,SMS_Unique_Identifier0 from UnknownSystem_DISC Using the returned GUID (SMS_Unique_Identifier0) we can find the hostname that has been assigned the 'x64 Unknown Computer (x64 Unknown Computer)' GUID by running the query below. --x64 Unknown Computers select Name0,SMS_Unique_Identifier0,Decommissioned0 from Sys...

Windows 7 Offline files will not go Online when connected to network

Issue Several laptop users move between networks, domain, home, etc and when they attempt to access DFS shares explorer status is working offline.  The issue only resolves it self after a reboot. Connecting directly to the share works and i am able to ping network resources.  This behavior occurs for VPN users as well. Possible Causes "slow-link mode". In win7 (with default settings) a client will enter slow-link mode if the latency to the server is above 80ms. In slow-link mode all writes are made to the local cache and a background sync only happens every 6 hours.  Depending on your connection the default slow link detection speed is 64,000 bps On client computers running Windows 7 or Windows Server 2008 R2, a shared folder automatically transitions to the slow-link mode if the round-trip latency of the network is greater than 80 milliseconds, or as configured by the "Configure slow-link mode" policy. After transitioning a folder to the slow-link mode, Offline Fil...

SCCM Software Update - Job error 0x80004005 Failed to Add Update Source for WUAgent

SCCM Software Updates - Failed to Add Update Source for WUAgent  Today I have been looking at a range of servers (Server 2008 /R2 2012 /R2) that were failing to communicate with the Software Update Point (SUP) in SCCM and retrieve deployment policy. The UpdateDeployment.log was reporting the Job error 0x80004005 Job error (0x80004005) received for assignment ({af7a48e6-d550-4070-dd9b-ecc234567584}) action UpdatesDeploymentAgent 12/6/2017 10:32:27 AM 2096 (0x0830) The WUAHandler.log  was reporting "Unable to read existing WUA Group Policy object" and "Failed to Add Update Source for WUAgent " Unable to read existing WUA Group Policy object. Error = 0x80004005. WUAHandler 12/6/2017 3:41:00 AM 2828 (0x0B0C) Failed to Add Update Source for WUAgent of type (2) and id ({3AAB6A76-CE2D-4E8A-9F11-123AE69612A1}). Error = 0x80004005. WUAHandler 12/6/2017 11:03:31 AM 2276 (0x08E4) Until the agent can report back to the SUP, SCCM will not be able to summarize Software Update sta...