superatticman Posted February 11, 2015 Posted February 11, 2015 Hi all We are building a number of new system images from scratch. I plan to install Solus 3 client on the system image prior to closing and running 'sysprep' for deployment. Has anyone come across any issues post sysprep when using Solus 3? Was planning on also installing SIMS onto the system image via Solus 3 and then running sysprep but am wondering how the Solus console would handle a number of new computer names which originally came from one source PC. Or am I looking at closing the image prior to installing Solus 3 and SIMS and then pushing out afterwards to each individual machine? Cheers.
carmeruk Posted February 12, 2015 Posted February 12, 2015 I wouldn't. Sorry capita if you're listening, but why is Solus so dns horrid? As a rule nothing that can deploy goes anywhere near an image. What's the point? For me image building these days is an exercise in default Account management rather than wholesale software installs. Maybe the odd driver but that's about it. Certainly not Solus. That's my two penneth and I'm sticking to it!
synaesthesia Posted February 12, 2015 Posted February 12, 2015 No, I wouldn't either. There's no need; solus 3, when correctly set up and when your DNS is working as it should, is easy enough to push out without having to bundle in with your image. Besides which, you'll either end up updating your image 3/4 times a year just for SIMS; it makes the whole idea rather pointless.
SHimmer45 Posted February 12, 2015 Posted February 12, 2015 we were advised against including it it images
superfletch Posted March 22, 2016 Posted March 22, 2016 (edited) Dredged up this thread from a year ago as a lot of people are having to install S3 at the moment and it was one of the similar threads on the recent post... Don't include S3 agents on an image - the agent includes a GUID (unique identifier) which identifies it in the S3 database, that will go badly wrong if all your imaged machines are reporting back to the database as being the same machine. Agree about the DNS horribleness. Include the correct .net framework in the image and perhaps the firewall requirements (or send them from GPO). Edited March 22, 2016 by superfletch
SHimmer45 Posted March 22, 2016 Posted March 22, 2016 we install after an image is applied due to reasons above
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now