DrBeaker Posted February 12, 2019 Posted February 12, 2019 I know this is an old thread but AFAIK still as of Feb 2019 this hasn't changed. This is the way I've been told to build machines and "reinstall" SIMs.
jonnykewell1 Posted February 12, 2019 Posted February 12, 2019 If I remember rightly all I did last time was remove the Computer from solus, delete its old entry from DNS and then add the new machine in solus and all worked fine. Give it a try.
FishCustard Posted February 12, 2019 Posted February 12, 2019 All the more reason to dump SOLUS 3 and use PowerShell to deploy SIMS/FMS. Happy to supply my script if needed. SOLUS 3 is, and has always been, user-hostile rubbish for client deployment. Fine for updating and patching servers, but useless for clients.
DrCheese Posted February 12, 2019 Posted February 12, 2019 It is somewhat nuts that when reimaging a machine, you have to go and delete it - Then redeploy the agent/SIMS apps out after. For Sophos, I just have an install script that checks if sophos is already on the machine and runs the deployment if not. Picks up reimaged machines without fail every single time. In conjuction with the auto deploy/sync built into enterprise console it just.. works Solas is a heap of garbage.
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