RIS - One build to rule them all? (sad Tolkien ref)

[SpuffMonkey]

@ajbritton. You are not using the scripts correctly. A properly configured .sif file will do all of the domain joining, and XP config for you, negating having to do it yourself.

 

Can any of you RIS guys point us to some good RIS explanatory sites that'll lead RIS newbies through the stuff?

[tosca925]

Try a few of this

 

http://support.microsoft.com/kb/891128

[ajbritton]

@ajbritton. You are not using the scripts correctly. A properly configured .sif file will do all of the domain joining, and XP config for you, negating having to do it yourself.

 

Let me correct myself! When I say that 'my PCs go through the same setup sequence', I mean that the 'automatically' go through the setup sequence, adding themselves to the domain and so on. I was just trying to point out the timings of the various bits of the RIS installation. My PCs still take 15 to 20 minutes to build themselves, showing the same XP setup screens, but not asking me any questions. When the setup completes, the PCs reboot, pick up group policy settings, install assigned software, then do an auto-logon and use the RunOnceEx method to install any software included in the build (e.g. PowerDVD, Roxio or Nero).

 

NB - I am NOT using RIPREP to create my builds. Could this be why they are slower???? :?

[Ric_]

@AJ: You must just have slow machine (3GHz P4s with 512MB RAM on a full duplex gigabit connection straight to the switch where the server is and virtually no network traffic!)

[Dos_Box]

@ajbritton. Use ripprep on a complete build. That way you know everything is set ok and will install as standard. It doesn't take much to update this image once completed.

[Ric_]

AJ's method of MSIs through GPOs does have its benefits. If an installation becomes corrupt in some way, the MSI will rebuild the installation automagically.

 

I know that managed workstations should also do this but I'm unsure about how they would handle it if you have a huge number of apps installed in your RIS image.

[ajbritton]

The reason I have avoided RIPREP is because I want my builds to be 100% clean every time and not accumulate the cruft associated with an image which evolves over time (new programs added, old ones removed, updates etc.). Downside to this method is every application has to be in MSI format which can mean repackaging and lots of messing about. I provide support to lots of schools though, so I usually get to reuse repackaged applications.

[Ric_]

@AJ: I see where you're coming from. That's why I tend to only build them with the big/awkward progs. If you only have a few types of PC you can usually get away with re-creating your images quite regularly.

[StewartKnight]

This is a proper Tolkien reference!!!

[tarquel]

@ABJ:

 

Why does every app have to be in MSI format tho?

 

(to answer myself tho, I assume this is because you use only GP to deploy applications)

 

I have only got the User Hive unload thing on the GP deployment lol

 

Regards

Nath

[ajbritton]

@tarquel: Yes, that's right. All software is deployed with AD. I create OUs and policies which install the appropriate software on the appropriate PCs. If I need to get a certain piece of software on just a handful of machines (say 3 of the 16 machines in the ICT suite) then I create a new GPO and filter it using machine group membership - it's a little bit icky but it does the trick.

 

There's actually quite a lot of software that comes in MSI format and is ideal for deployment with AD. MS Office, Acrobat Reader, Sun JRE, DaemonTools to name but a few.