Jump to content

Recommended Posts

Posted

Hi guys,

 

I'm now discovering the joys of SOLUS3 having just had it installed on our network.

 

I have rebuilt a workstation wit the same name and have now gone into SOLUS3 to try and re-deploy SIMS applications to it. It was failing to communicate with the agent so I removed the "target" and went to Update Environment to add the "target" back in but it is not showing!

 

The instructions say that as it is AD integrated that it should be listed. I was told adding the target client to a channel was the way to deploy the applications?

 

Any help or advice would be greatly appreciated. :)

Posted
If you rebuild a machine, you have to 'completely' remove the agent and then re-add the device, not just remove it from the SIMS channel then re-add it. In the list of Agent devices, remove the workstation in question using the 'Remove' button then add the device again from scratch.
Posted

Yes I clicked remove computer on the Deployment Environment list - Agents tab.

I did not click Uninstall agent as the CC4 computer was rebult.

But now when I go into the Update Environemtn Screen I cannot find the computer to re-add it. :(

Posted
When you try to add the workstation back to the SIMS Channel, how do you find it? Browse AD or brose Network Computers? As long as the workstation is online and has no firewall/DNS issues, it should be listed in the 'Browse Network Computers' browser.
Posted

I'm choosing a channel, clicking "Select Computers" > "Add"

The computer is not listed. Nothing under Browse Network Computers. Not present under Browse Agent either.

Yet the business manager is using her computer and it is showing in the RM Management Console with packages assigned to it.

Posted
If it's not got an agent yet, it won't be under the "Browse Agent Computers" area. If it's not listed under the network computers browser, sounds like either firewall or DNS are not quite right. Tried adding it manually at the bottom by hostname or IP?
  • Thanks 1
Posted

Sometimes the browse AD computers seems to just "not work" when the computer is not in an OU, just in top level.

Never got to the bottom of the why?

Moving a computer into a "temp" OU in AD sometimes enables the AD computer to be "seen" by Solus3

You can move it back where you want after its been put into solus3

But it is a workaround......

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...