Jeroen van Geem

Hi all, I managed to pull drivers and firmwares from Dell through SCUP (published 'full content') into SCCM. I added these to a 'software update group', and downloaded these to a package and distributed that package. Then I went back to the 'software update group' and deployed it (as 'available') to a collection containing 2 servers. So far so good. But now when I check the servers I dont see anything in the Software Center. Nothing comes in into the C:\Windows\ccmcache directory as well. Someone an idea what I am missing? Thanks!

Fixed by running the task under a domain account with SCCM access instead of the built-in system account.

Anyone?

Hmmm, it doesnt seem to find the resourceID eventhough the %_SMSTSClientIdentity% gets resolved correctly.

Thanks, will give that one a go. During deployment, after the SCCM client gets installed this script will run maybe one minute after that. Does this give the SCCM server enough time to have the server currently being deployed to be added in its repository? I do know it takes time before a new deployed system shows in the gui.

Hi all, I am trying to achieve the following during my OS deployment; Add the device into a collection followed by running some patching cycles. However I cant seem to figure out how to add the device into a patching collection. I found a vb script out 2010 online (attached) which I used, but no luck. This is the line: cscript c:\Installs\Tools\AddMeToCollection.vbs xxxxxx "GLB - Patch Sunday 05:00 - Reboot" %_SMSTSClientIdentity% Are there any new ways to make this possible? Once it is in the collection I was planning on running the following twice: Run script: WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000113}" /NOINTERACTIVE Run script:powershell.exe -command start-sleep 30 Install Software Updates (built-in task) But without the system being in a collection it wont do anything. Any ideas? Thanks! 2134.AddMeToCollection.txt

Hi, Our organisation is pretty big and after we fill in the computername in the HTA form a cvs file is queried where based on the computername other variables are being created. So unfortunately we are in no position to use collection variables. When you were running into similar issues, what exactly did you encounter and what did you tried to resolve it? My workaround will be something like: Keep the "Apply windows settings" task sequence Fill in User name, Organization name and set the default password in that task sequence and removing these conflicting entries from the sysprep file However, I just want to know what is happening in the background and why it doesnt work like its supposed to do.

Dear all, I am currently in the process of transfering our current deployment platform to SCCM and am now stumbling accross an issues I dont seem to be able to solve by myself. Server name not set We set the OSDComputerName variable during the HTA processing and have this variable in our sysprep file. For some kind of reason -while this variable is confirmed existing (I have a small vb script that allows me to dump all variables in a txt file)- the SCCM task sequence doesn’t change the variable into the computername, but removes the whole “Computername” line. The end result is an auto generated computername. Attached our Autounattendvariables.xml and the unattended.xml file SCCM finally uses (was able to recover it before the systems reboots and deletes the file). Autounattendvariables.xml unattend.xml Note After adding a 'Apply Windows Settings' task sequence the computername does work. However, the User name, Organization name and local administrator settings are overwriting the settings already in my unattended file. The time zone setting in the unattended file however doesnt get overwritten by the setting in the task sequence. So not consistent behaviour in any way... Task sequence screenshot (after adding 'Apply Windows Settings'): Is there someone out here who can bring light into the darkness? Regards, Jeroen