Re: OS deployment feature pack
From: Brett Flegg \(MS\) (bflegg_at_online.microsoft.com)
Date: 11/25/04
- Next message: Darren: "SMS Admin console on site server"
- Previous message: Greg Milne: "Software Inventory doesnt read E:\ on file & print server"
- In reply to: lramsdale: "Re: OS deployment feature pack"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 25 Nov 2004 13:19:00 -0800
Hi,
When doing an in-place deployment, the Image Package/Program will always
install Windows PE and logs to C:\minint (so you will need to make sure you
have some free space on C). By default USMT state is also stored in this
directory, but you can set the OSDSTATEPATH to whatever you want (in your
case, a place on your second partition with a custom action like [osdenv
"OSDSTATEPATH=D:\userstate"]). Please note that when you are doing an
in-place deployment you can not re-partition the disk so any image that you
deploy will have to fit on the 4Gb partition.
-- Brett
-- brett flegg | software design engineer/test | SMS | OSD FP This posting is provided AS IS with no warranties and confers no rights. "lramsdale" <lramsdale@discussions.microsoft.com> wrote in message news:A44236DC-E73E-45A8-A526-6DD6E471243D@microsoft.com... > Thanks I had not read that section in the documentation. The reason i am > considering the network is that many of the machines have limited disk > space > on the c drive. For whatever reason the w2k build has only a 4GB partition > where the OS is installed. When the USMT runs locally is there a default > location where it places all the data? Can this be relocated to a specific > local drive? > > "Brett Flegg (MS)" wrote: > >> Hi, >> >> In the future, please use the microsoft.public.sms.tools newsgroup for >> OSD >> questions. >> >> To use USMT with OSD you will need to add USMT save/restore actions in >> the >> State Capture and State Restore phase respectively. By default, the OS >> Deployment Feature Pack saves the user state locally on the destination >> computer. This is the most secure location for the state and does not >> impact >> the network or require you to configure servers with appropriate security >> permissions and available disk space. If you need to store the user >> state >> on the network, you can use a custom action to set the OSDSTATEPATH >> variable >> to a network location. Check out the "Planning for User State Migration" >> section in the OS Deployment FP guide for more information and let me >> know >> if you have any more questions. >> >> -- Brett >> >> -- >> >> brett flegg | software design engineer/test | SMS | OSD FP >> >> This posting is provided AS IS with no warranties and confers no rights. >> >> >> "lramsdale" <lramsdale@discussions.microsoft.com> wrote in message >> news:A652C67F-CE4E-4C3F-A0BC-155CBD3BA2A2@microsoft.com... >> > Apologies if this is not the correct newsgroup... >> > >> > I am a little confused about the USMT and how this integrates with the >> > OS >> > deployment feature pack. >> > >> > I am not sure whether I am just lazy or the documentation is a little >> > muddy. >> > If I want to perform an in place upgrade and migrate the users settings >> > to >> > a >> > network share what steps do i need to perform? >> > >> > So far I have created the image, setup the package and configured the >> > program with the relevant details. In the advanced section of the >> > image >> > program I have specified a folder with the USMT 2.6 files for the state >> > capture phase and configured the state restore. >> > >> > What do I need to do in order to save the users files to a network >> > share >> > then restore them during the state restore phase? >> >> >>
- Next message: Darren: "SMS Admin console on site server"
- Previous message: Greg Milne: "Software Inventory doesnt read E:\ on file & print server"
- In reply to: lramsdale: "Re: OS deployment feature pack"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
