 KilroyPremium,MVM
join:2002-11-21
Ann Arbor, MI | reply to Badger3k
Re: [Info] Ghost Sysprep What OS?
You need to run the Setup Manager before you Sysprep, every time, to create the Sysprep directory that is deleted on the install. The SYSPREP.INF file needs to be in the same directory that you are launching SYSPREP.EXE from.
--
I have two favorite sports teams, University of Michigan and whoever is playing Michigan State. |
|
 Badger3kWe Don't Need No Stinkin BadgersPremium
join:2001-09-27
Franklin, OH | said by Kilroy:What OS? You need to run the Setup Manager before you Sysprep, every time, to create the Sysprep directory that is deleted on the install. The SYSPREP.INF file needs to be in the same directory that you are launching SYSPREP.EXE from. We're using XP. Yeah, I figured out you had to have that directory each time you want to take the image. Only took me 2 tries to realize I need to save my .inf file someplace other then the test machine. 
--
Team Discovery: Project Hope | ET is out there, can you find him? |
|
KilroyPremium,MVM
join:2002-11-21
Ann Arbor, MI | You can store the SYSPREF.INF file on the machine, just make sure it is out of the created Sysprep directory. For instance my company's standard is to store IT files in C:\Windows\System32\ITS. Inside of that folder I keep a Drivers folder with separate folders for each driver, a Sysprep folder with Sysprep and Setup Manager, a change log, and some other things. I have a batch file to launch the Sysprep. Here are the contents of that file.
After I Sysprep the machine I make an image and then verify the image. If there is a problem I fix the problem, rename SYSPREP.INF, run Setup Manger (you can't short cut it, you have to put in all of the information), delete the SYSPREP.INF and rename my previous SYSPREP.INF, Sysprep, and reimage. (I have an OemPnPDriversPath line that points to the drivers directories and it is just easier to keep reusing that SYSPREP.INF rather than redoing it every time.)
Things I have learned:
You can delete the page file and defragment the drive before you Sysprep, a new "default" page file will be created after going through the mini set up. This will make your images smaller.
Certain things will be turned back on, no matter how you had them set in your image, System Restore will be on for all drives and Start up and Recovery settings will reset to the defaults. I'm sure there are more, but these are the ones I've noticed.
--
I have two favorite sports teams, University of Michigan and whoever is playing Michigan State. |
|
|
|
Badger3kWe Don't Need No Stinkin BadgersPremium
join:2001-09-27
Franklin, OH | said by Kilroy:You can delete the page file and defragment the drive before you Sysprep, a new "default" page file will be created after going through the mini set up. This will make your images smaller. I think there is an option you can set in the sysprep.inf file that will automaticly skip the page file. It's in one of the links NyQuil Kid  posted. I think it's KeepPageFile=0 or something to that extent.
This probably gets into whole nother topic, but do you guys have any sort of Deployment packages? If say a user needs Application XYZ, that isn't part of the standard image, you just install from a Rip stored on a network share or do you use something like Ghosts AI Package builder?
--
Team Discovery: Project Hope | ET is out there, can you find him? |
|
KilroyPremium,MVM
join:2002-11-21
Ann Arbor, MI | We use Novell NALs for most of the non-standard loads, some manual for the really off the wall stuff.
The real bite is trying to keep the images up to date. You figure Microsoft releases every second Tuesday and then any other software that is part of your standard, i.e. Java, Adobe, etc. It can be a full time job.
--
I have two favorite sports teams, University of Michigan and whoever is playing Michigan State. |
|
 NyQuil Kid8f The Nyquil Kid
join:2001-01-06
Brick, NJ | reply to Badger3k
At my previous position, we also used Novell for a great deal of the post image app installs. However, in my experience I preferred to manually install and configure.
For example, our end users were given limited user level rights - there was a program that required some changes in user permissions to work properly; the only way we knew that was to install it manually on an imaged PC and play with it.
[8F] The NyQuil Kid
--
[8F] The NyQuil Kid comes into town not looking for trouble...n00bz gang up, but he ain't seein' double,...pulls and draws, his deagles two...n00bz litter the ground you know it's true. |
|
