Jump to content

Recommended Posts

Posted
Flaky as in sometimes it won't add to domain giving me a silly error (net path 53 ) I think. Then sometimes a few drivers need clicking yes on the install section. That's just a little niggle of mine. Apart from that it does everything I need.

 

Not had issues with either of those. Are you installing drivers as snapins with silent installs? Or are you including them in the base image?

Posted

drivers are on the base image.

 

what do you do if you have something that needs to be install after deploy (an exe) but needs dos commands parameters to install?

Posted
Drivers and all software are all in the base image but its a hardware agnostic image that can go on a number of machines using sysprep and a few other tools. I just never set it to silent install all the drivers my bad I just haven't had chance to fix it. My main problem is it doesn't always join the domain.
Posted
drivers are on the base image.

 

what do you do if you have something that needs to be install after deploy (an exe) but needs dos commands parameters to install?

 

You create a snapin. You can run batch scripts from there, or you can use installrite to make a simple installer, or you can use SFXMaker to make an installer containing a folder which runs, or rustle up an MSI.

 

Lots of options really!

 

Drivers and all software are all in the base image but its a hardware agnostic image that can go on a number of machines using sysprep and a few other tools. I just never set it to silent install all the drivers my bad I just haven't had chance to fix it. My main problem is it doesn't always join the domain.

 

Ah, yeah, I've been spending a few weeks building our new image and snapins of all our software to install silently, but I totally appreciate that most people don't have that time to spare.

 

Really not sure why your machines wouldn't always be joining the domain though!

Posted

2 weeks to test (if possible), 100 (different hardware?) workstations + server/network upgrades/reconfigure. And they gave 3 weeks to complete (1 if not allowed downtime on any machines)!!!.

PXE boot can be interesting to start - Check over the next few weeks/days to see if machines will actually boot off network, this can seriously affect deployment time.

Building Images from scratch - sure all/different drivers will be needed to be sourced wether ghost or whatever deployment used.

 

Good luck

Posted

Just sorting out a FOG server. Gave up on WDS.

Anyone got a step by step of creating an image, if not I will have a better look at the FOG wiki.

Cheers

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...