round2it Posted September 25, 2018 Posted September 25, 2018 Hi All Is it possible to install solus 3 on a non domain joined pc we currently have a windows 7 domain one of our staff have a windows 10 pc that they use at home but they require sims to be available when in school. as I have not done anything with windows 10 gpo wise I do not want to connect to the domain just yet I have exported the installer from solus 3 and installed on the client I have then added it to solus 3 ui unfortunately on the solus 3 ui it appears the console can not connect to the client even with the firewall off and uac down to lowest level does anyone know what might be the issue I can ping the server from the client via name and ip also I can ping the client from the server the same I do get a message saying it can not save a config file as it already exists
Esteban_Child_of_the_Sun Posted September 25, 2018 Posted September 25, 2018 Hi round2it. Yes SOLUS3 does work with non-domain machines, we usually get the local admin account for the PC and push the SOLUS3 client on from the server as the username and password SOLUS asks for when installing clients is local to each machine, usually with domain workstations this is the same for all as we use a domain admin with local admin permissions.
round2it Posted September 25, 2018 Author Posted September 25, 2018 that was going to be my next thing to try do you use username or workgroupname/username
Esteban_Child_of_the_Sun Posted September 25, 2018 Posted September 25, 2018 just username will use the local machine's users
round2it Posted September 25, 2018 Author Posted September 25, 2018 I will uninstall and give it another go. once added to solus 3 I can click and browse to the pc so the connection is present it must be permissions
round2it Posted September 25, 2018 Author Posted September 25, 2018 I give up gonna sort the gpos out
Cache Posted September 25, 2018 Posted September 25, 2018 (edited) For our non domain machines I just export the installer from Solus 3, manually install on the laptop and then use it to add the targets from an existing agent. Also handy for reinstalling Solus3 on a machine that's been reimaged. The only thing I do manually with the firewall is add the 3 executables as exceptions so the package deployer, agent ui and offline deployer. I don't know if you need all 3, however the only issue I've had is when the deployment tries to being but the firewall isn't configured correctly, it sometimes for whatever reason won't time out doing what it's doing until several hours later. Edited September 25, 2018 by Cache
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