Copying Local GroupPolicy via a TS on SA Media

[P@docIT]

Has anyone done any Local GroupPolicy settings via stand alone media OSD? Unfortunately the environment I work in does not allow for PXE deployment and since I don't control the network I'm stuck with deploying via media. The workstations are part of a domain and will have Group Policy applied, however there are few small items that I would have to beg our GP admin to add, sometimes it's easier to just do it locally.

 

So I set my GP on a machine and copied the GroupPolicy folder from %SYSTEMROOT%\System32. I've tried a few ways to copy this folder back to the a fore mention path on the new machine. Robocopy worked but every time you would run gpedit it would give a permission denied message. All permissions looked perfectly fine. So I found a script that someone wrote that copies all files in the same dir as the script to a specified location. It works if run manually from the local machine, however if i try and run it manually from the OSD Media it gives me an access denied message when trying to copy.

 

Just wondering if anyone has any ideas or if anyone is currently doing this for maybe stand alone machines.

 

Location of the copy script i am currently trying to use: http://blog.coretech.dk/mip/making-file-copy-easy/

[anyweb]

you can do it like so along as you have integrated MDT 2010 update 1 with SCCM 2007. Create a sub folder off of your scripts folder in MDT Toolkit files package, then copy the group policy files from a computer that has had the policies applied,

in order to use this you must then have a Use Toolkit Package

 

the actual copy command (Run Command Line) is like so

 

xcopy.exe "%deployroot%\scripts\Customscripts\GroupPolicy" "c:\" /E /C /I /Q /H /R /Y /S

 

and must take place BEFORE the Setup Windows and configmgr Step

 

cheers

niall

[P@docIT]

you can do it like so along as you have integrated MDT 2010 update 1 with SCCM 2007. Create a sub folder off of your scripts folder in MDT Toolkit files package, then copy the group policy files from a computer that has had the policies applied,

in order to use this you must then have a Use Toolkit Package

 

the actual copy command (Run Command Line) is like so

 

xcopy.exe "%deployroot%\scripts\Customscripts\GroupPolicy" "c:\" /E /C /I /Q /H /R /Y /S

 

and must take place BEFORE the Setup Windows and configmgr Step

 

cheers

niall

 

Thanks Niall,

 

Please forgive my noobness. I am very new to sccm. The previous admin left for a new job and I have had minimal training. Also the server was setup long before I got involved. How can I tell if MDT 2010 Update 1 has been integrated?

 

update: OK i am pretty sure that MDT 2010 update 1 has been integrated. Now I am stuck on "Create a sub folder off of your scripts folder in MDT Toolkit files package". I am not clear on how to accomplish that step, the rest of the steps I understand.

[P@docIT]

Thanks Niall,

 

Please forgive my noobness. I am very new to sccm. The previous admin left for a new job and I have had minimal training. Also the server was setup long before I got involved. How can I tell if MDT 2010 Update 1 has been integrated?

 

update: OK i am pretty sure that MDT 2010 update 1 has been integrated. Now I am stuck on "Create a sub folder off of your scripts folder in MDT Toolkit files package". I am not clear on how to accomplish that step, the rest of the steps I understand.

 

Well I figured out how to add all the parts I need. We had an MS partner come in and show us how to use OSD and he setup the initial Task Sequence. Attached is screenshot of what i have. All works with the exception of the GPO copy.

 

My question now is am I creating two steps for use toolkit and run command line? I don't see an option to run a command in the use toolkit package.

 

Thanks,

Mike

[anyweb]

correct two steps

 

step 1. use toolkit package

step 2. xcopy gpo's

 

the toolkit package has several files/folders one folder is called scripts, copy your customscripts folder (and subsequent folders/files) to the scripts folder so the package is now

 

\\server\sources\MDT Toolkit package\scripts\customscripts\group policy

 

then update that package to it's dp's

 

then test the task sequence

[P@docIT]

correct two steps

 

step 1. use toolkit package

step 2. xcopy gpo's

 

the toolkit package has several files/folders one folder is called scripts, copy your customscripts folder (and subsequent folders/files) to the scripts folder so the package is now

 

\\server\sources\MDT Toolkit package\scripts\customscripts\group policy

 

then update that package to it's dp's

 

then test the task sequence

 

That didn't work for me and unfortunately i have no logs to check. My last task sequence sets the machine up to remove SCCM. We have about 7000 machines across the state and not all of them have been moved from SMS to SCCM yet. So to keep this image usable across the board we remove SCCM.

 

Do I need to point the run command line sequence to the MDT toolkit package? I originally assumed that was the point of the use toolkit package sequence.

[anyweb]

well pause a machine by pressing f8 and grab the logs before that step

without the logs I can't really advise you

[P@docIT]

well pause a machine by pressing f8 and grab the logs before that step

without the logs I can't really advise you

 

Yeah I realize that i will need the logs I am just going to disable that last step for now until I figure this out. In the mean time, can you tell me if I need to point the "run command line" step (see above screenshot of my TS) to the MDT Toolkit package or does the use toolkit package step take care of that?

[anyweb]

no you dont, the Use Toolkit package step immediatly before that takes care of it

[P@docIT]

no you dont, the Use Toolkit package step immediatly before that takes care of it

 

Don't know if this helps or not. I tested pointing the "run command line" step to the MDT package before you replied that I didn't need to. Below is the log from that test. The result on the PC is an empty GroupPolicy folder this time. I will be running another test without pointing the "run command line" step to the MDT package so I can see what the log says.

 

 

Parsing step node: Use Toolkit Package TSManager 8/8/2011 1:03:47 PM 208 (0x00D0)

Description: TSManager 8/8/2011 1:03:47 PM 208 (0x00D0)

ContinueOnError: true TSManager 8/8/2011 1:03:47 PM 208 (0x00D0)

SuccessCodeList: 0 TSManager 8/8/2011 1:03:47 PM 208 (0x00D0)

(__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\nts_sms_fre\SMS\common\inc\ccmxml.h,566) TSManager 8/8/2011 1:03:47 PM 208 (0x00D0)

No condition is associated with the step. TSManager 8/8/2011 1:03:47 PM 208 (0x00D0)

Disable: TSManager 8/8/2011 1:03:47 PM 208 (0x00D0)

Start in dir: TSManager 8/8/2011 1:03:47 PM 208 (0x00D0)

Run in attribute: WinPEandFullOS TSManager 8/8/2011 1:03:47 PM 208 (0x00D0)

Timeout: TSManager 8/8/2011 1:03:47 PM 208 (0x00D0)

DefaultVarlist found TSManager 8/8/2011 1:03:47 PM 208 (0x00D0)

No variables found in default variable list TSManager 8/8/2011 1:03:47 PM 208 (0x00D0)

Action command line: smsswd.exe /run:CR200063 cscript.exe Scripts\ZTISCCM.wsf TSManager 8/8/2011 1:03:47 PM 208 (0x00D0)

Adding instruction at 9 TSManager 8/8/2011 1:03:47 PM 208 (0x00D0)

 

Parsing step node: Run Command Line TSManager 8/8/2011 1:03:47 PM 208 (0x00D0)

Description: TSManager 8/8/2011 1:03:47 PM 208 (0x00D0)

ContinueOnError: true TSManager 8/8/2011 1:03:47 PM 208 (0x00D0)

SuccessCodeList: 0 3010 TSManager 8/8/2011 1:03:47 PM 208 (0x00D0)

(__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\nts_sms_fre\SMS\common\inc\ccmxml.h,566) TSManager 8/8/2011 1:03:47 PM 208 (0x00D0)

No condition is associated with the step. TSManager 8/8/2011 1:03:47 PM 208 (0x00D0)

Disable: TSManager 8/8/2011 1:03:47 PM 208 (0x00D0)

Start in dir: TSManager 8/8/2011 1:03:47 PM 208 (0x00D0)

Run in attribute: WinPEandFullOS TSManager 8/8/2011 1:03:47 PM 208 (0x00D0)

Timeout: TSManager 8/8/2011 1:03:47 PM 208 (0x00D0)

DefaultVarlist found TSManager 8/8/2011 1:03:47 PM 208 (0x00D0)

Variable name: SMSTSDisableWow64Redirection TSManager 8/8/2011 1:03:47 PM 208 (0x00D0)

Variable name: _SMSTSRunCommandLineAsUser TSManager 8/8/2011 1:03:47 PM 208 (0x00D0)

Action command line: smsswd.exe /run:CR200063 xcopy.exe "%deployroot%\scripts\CustomScripts\GroupPolicy" "%SYSTEMROOT%\System32\" /E /C /I /Q /H /R /Y /S TSManager 8/8/2011 1:03:47 PM 208 (0x00D0)

Adding instruction at 10 TSManager 8/8/2011 1:03:47 PM 208 (0x00D0)

[anyweb]

parsing step node simply means it's reading the task sequence steps before actually running them, what you need to look for is Start Executing Use Toolkit Package, do you see that anywhere ?