Hello. We're beginning to do some work with deploying Windows 7 in our environment. It was suggested that with the KBOX that employing a scripted install might be a better route to go than a traditional Sysprep captured image. We have most of our applications already running as post install tasks anyway that aren't part of the image, but I have a couple questions about best practices for the KBOX with respect to Windows 7 scripted installs.

1. How should the default user profile be handled? What's the best method to create, store, deploy the profile in conjunction with a scripted install?

2. Any other significant differences or adjustments that would need to be made to post install tasks or other aspects of how the final deployment is handled vs. a sysprep captured image?

Thanks.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Is there a preferred method of bundling the ntuser.dat file for xcopying? I have the file sitting on a network share, and in the batch file I have the following line specified:

xcopy \\bwsfile1\install$\kace\ntuser.dat "C:\Documents and Settings\Default User\ntuser.dat" /H /R

During the postinstallation, the command box just sits there executing the task and doesn't go anywhere.

Thanks. Wayne
Answered 06/08/2011 by: jwdima
Senior Yellow Belt

Please log in to comment
0
Yes, I'm sorry, it is XP. I am a little unclear on how to package. Will this change the xcopy paths?
Answered 06/08/2011 by: jwdima
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity