OSD WXP Image Question

OSD WXP Image Question (Full Version)

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager

Message

rjarrett -> OSD WXP Image Question (6/6/2008 3:38:29 PM)
I have a WXP SP2 reference computer. It has been activated. With SYSPREP you can specify whether to reset the activation or not. Thus, a Ghost of that image will create a machine that is already activated, per the licensing agreement. Specifically, if you use the -activated parameter... -activated - Do not reset the grace period for Windows product activation. Use this parameter only if you have activated the Windows installation in the factory. The SCCM OSD capture media uses SYSPREP, but does not allow you to retain the activation. Any thoughts? Is there a way to pass this argument so that the WIM is activated?

jsandys -> RE: OSD WXP Image Question (6/7/2008 3:19:15 PM)
Per what license agreement? The point of OSD is to roll out fresh (or refreshed) systems that do not have to be activated because they are volume licensed. Are you using an OEM or shrink-wrapped version of XP? Check out the following article on XP and sysprep: http://technet.microsoft.com/en-us/library/bb490244(TechNet.10).aspx.

wbracken -> RE: OSD WXP Image Question (6/7/2008 4:58:01 PM)
In order to "duplicate" an image in XP you need to be using a Volume License key which that switch has no bearing on. It is not legal (to my knowledge) to capture an OEM build and distribute it (if thats what media/keys your using). If you not under a Volume license agreement then imaging becomes quite a challenge. Microsoft has mutliple Volume Licensing models that can be tailored to suit even small organizations.

rjarrett -> OSD WXP Image Question (6/9/2008 9:34:14 AM)
SYSPREP specifically addresses situations where you are using an "activated" operating system instance (i.e. non-OEM) in its documentation. Even Microsoft recognizes that customers may have legitimate licensing scenarios that permit deployment of activated images. That's why the "-activated" switch exists. I am testing the deployment procedures using MSDN media in order to work through the bugs of SCCM OSD. When the time comes to implement this technology, we will need to build images that don't require activation. So, my question is simple, not sinister. Is there a way to "pass" the activated argument to SYSPREP via the OSD capture? When I am demonstrating this imaging process, I want it to come up the way the typical user will see it.

wbracken -> RE: OSD WXP Image Question (6/9/2008 10:20:20 AM)
Hey Rob, Just to clarify, I wasn't trying to imply you were intentionaly trying to buck the system. [:D] Just wanted to throw it out there just in case you were using OEM. Back to the question.. If your using MDT 2008 and you import the task sequence for capturing your base build, one of the last tasks in the sequence is "Prepare OS". One of the options on this task is: "Do not reset activation flag" Now I havent had to use this myself but it sure seems like that would be the equivalent of the -activated switch. I would give it shot. :)

rjarrett -> RE: OSD WXP Image Question (6/9/2008 10:37:44 AM)
William, If I am not using the MDT... First, should I be using it? Why? What advantages? What do you do with it that makes it worth an extra layer to go wrong? Second, is there a corresponding setting somewhere in the SCCM-pure OSD Task Sequence that does the same thing or am I just missing it? I will check again.

wbracken -> RE: OSD WXP Image Question (6/9/2008 11:01:19 AM)
I couldn't imaging using SCCM without it honestly. The "pre-packaged" Task Sequences that you can import do 75% of the Task Sequence work for you. The wizards walk you through creating all the dependant packages like USMT, SCCM Client, Sysprep, etc. teh felxability that you also get from teh CustomSettings.ini (or the AdminDatabase if you so choose) is really great as well. I also use the PXEFilter.vbs (albeit modified a bit) for imaging "Unknown Computers" until they release R2 which has it built in. Overall they way I see it is that Microsoft released SCCM with some good capabilities. Michael Neihaus' (Lead developer for MDT) team make it better. [:)] Not sure if there is a built in TS for doing this without MDT but I would image you could create your own Sysprep package, execute it via a Task passing your own perameters to it. Just make sure you use the proper restart switch with it as default I believe it will simply shutdown the machine after sysprep completes which would obviously throw off the automation of the process.

Page: [1]

Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

0.1875