I've added this to a larger script that I use, but if you only wanted to automate the naming process the above would work for you.

Else just remove the header #!/bin/sh and add the reset to any setup scripts that you have to automate this portion of the setup.

@stacksofplates I can imagine. Good luck!

Well that answers that. LOL Now I will have to redeploy to everyone and maintain different versions. Oh well. PDQ Deploy to the rescue.

@ambarishrh said in Centralized Imaging/OS Deployment:

Some of the features I liked on that is the base image is made from a virtual instance so that this can be deployed to any machine and a single image to maintain, the driver packs for almost every model etc. I am planning to evaluate this in detail next week when I am back in the office.

JB does this almost exclusively with Clonezilla. I've done it as well, so using a VM doesn't matter to the product.

My second choice would be MDT but again if SmartDeploy is taking the pain for spending a lot of time on the initial setup, which we don't have at the moment (lot of internal projects in the pipeline with tight deadlines)

You're trading money for time here. MDT makes you do all the leg work, you have to find and add the drivers yourself. SmartDeploy takes your money and does that work for you.

Marked as answered.

@Dashrender What's weird though is I've gotten them to work here and there despite using msiexec. BUT then I changed some things around (added spaces....spaces make life hell but I wanted to see if I had to use " " around the path or not...utter failure, upon changing things back....I broke the installs)

But yeah, I'm happy :)
Now I just need to add what I've figured out to the other programs, which a few auto-activate lol, testing will have to be live.
Ugh then I have to make more deployments for our Autodesk products, which actually isn't that bad..

@coliver said:

Holy crap. Where was this a few months ago when I was building my click-to-run installer? Thanks for the info.

Right?! You can even upload your own and tweak it using that interface instead of going back and forth between notepad and the crappy TechNet doc lol.

Another useful script there (and I have to find it to link it) is a reverse engineering script. So let's say you have a C2R deployment out there that you can't determine the current settings easily, it will build an XML file from that individual installation to tell you what's installed, update location, etc.. It's pretty cool stuff.