I'm looking at going for a desktop support job.

I did 3/4 years of desktop support from about 1998 and thinking back it might have been the only job I've done that I actually enjoyed!

Anyway, I was thinking about interview questions I might get asked.

Back in 1998 when I started as a junior we were using NT4 and used sysdiff builds for rolling out multiple machines. This always struck me as a terribly slow process and so when a colleague and I introduced Norton Ghost and we could build a machine in 5mins instead of 2/3 hours it was fantastic.
I appreciate the situations are different with different model PCs. WE bought about 1000 Dell GX1s so it was perfect!

IIRC with Win2000 there became a problem in that the SID number *had* to be unique and so Ghost could still be used but you had to use a SID changer. (IIRC we used Ghost Walker? to do this) but for some reason this was recommended against. I moved out of the team around this time so I never saw how things developed.

How was it done for multiple PC roll-outs?

The place I'm applying has, I'm told, XP machines. How is it done with XP?

And I'm sure even more fun is to be had with Vista and Win7!


Don't want to trip up on some basic like this at interview!

Cheers,
James



[Edited on 11/1/12 by James]

haha the SID problem never existed - it was some fool at microsoft that said it did, it was clarified around 2 years ago funnily enough (im not laughing at you by the way, I worked on the same principals for a long time)

PXE boot a norton ghost image is popular as it allows you to do hundreds of machines at once.

however with server tech moving on its rarely neccessary, group policies will let you do everything your talking about from the server - just connect a machine to the network with a base install of 7 pro from dell or whoever and as soon as its listed in active directory will take on all the settings it needs to and your jobs done

If I have missed anything let me know and I will try to answer - I run an IT support company


edit to add the link to the guy that found the SID myth
clicky



[Edited on 11/1/12 by MikeFellows]

build a kix script. you just build a script then it can be done centrally from one location.

www.kixtart.org

scripting is your friend

Google RIS, or windows deployment service, its a native feature since Server 200 i think?
I use Symantec Backup Exec System Recovery as it allows creation of a single desktop image but will install on any hardware as once the image is applied it runs the Windows OOBE to allow you to install drivers.

how would you identify it on AD if it had the same SID as another machine if you havent run ghost walker and SID changer etc????

quote:

---

Originally posted by MikeFellows
haha the SID problem never existed - it was some fool at microsoft that said it did, it was clarified around 2 years ago funnily enough (im not laughing at you by the way, I worked on the same principals for a long time)

PXE boot a norton ghost image is popular as it allows you to do hundreds of machines at once.

however with server tech moving on its rarely neccessary, group policies will let you do everything your talking about from the server - just connect a machine to the network with a base install of 7 pro from dell or whoever and as soon as its listed in active directory will take on all the settings it needs to and your jobs done

If I have missed anything let me know and I will try to answer - I run an IT support company


edit to add the link to the guy that found the SID myth
clicky



[Edited on 11/1/12 by MikeFellows]

---

how would you know the SID without physically visiting the machine?

read the article, its quite interesting - I havent changed a SID for ages now after reading that and have never had a problem. but like I say its been so long since I needed too as group policies now allow me to do everything I could ever need to

same as login/log off scripts - I still see people using these - totally un-neccessary nowadays

quote:

---

Originally posted by MikeFellows
how would you know the SID without physically visiting the machine?

read the article, its quite interesting - I havent changed a SID for ages now after reading that and have never had a problem. but like I say its been so long since I needed too as group policies now allow me to do everything I could ever need to

same as login/log off scripts - I still see people using these - totally un-neccessary nowadays

---

quote:

---

Originally posted by jossey

quote:

---

Originally posted by MikeFellows
how would you know the SID without physically visiting the machine?

read the article, its quite interesting - I havent changed a SID for ages now after reading that and have never had a problem. but like I say its been so long since I needed too as group policies now allow me to do everything I could ever need to

same as login/log off scripts - I still see people using these - totally un-neccessary nowadays

---

We just use a sid changer to give a random sid to the 4000 machines we manage in certain compaines.

Saves any AD issues. Ill try it without but always had issues with AD not identifying the machines if the sids are the same......

As far a login and log off scripts. we use them alot as you dont want 4000 machines pulling new updates of the server at the same time. eg when shops open like 4000 tills getting updates at same time when you can stangger the restart login etc to get the throughout the night.

This saved the company over 2 million in new server and line costs......


Anywho thanks for the article good find :O)

PS aint seen you in a while come over and see us.....

---

Look up on google about sysprep and OOBE (out of box experience) this deals with SSID also there is a long thread on google saying SSID doen't matter..... Contravental