Steve in MA Posted June 15, 2016 Report Share Posted June 15, 2016 I've just upgraded to SD 2.0.2000. I've manually installed the SDClient to a machine, specifying the name of my desktop as the console. I have yet to see the client machine appear in Computer Management. How does SD communicate to the console machine? The machines are are separate VLANs, and we do not allow broadcast traffic. I'm just wondering if it is something as simple as that, or if I need to dig deeper. Is there a log file on the client machine that I could check (I haven't found one yet)? Link to comment Share on other sites More sharing options...
SmartDeploySupport Posted June 15, 2016 Report Share Posted June 15, 2016 Hi Steve, You need to specify a host name or IP address when you install the SmartDeploy Client. If they are on separate VLANs, and you do not allow traffic between the clients on one VLAN and the console on another, that would prevent push deployments initiated from the console (as well as other network-based deployments initiated from the client-side) from functioning properly. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL Link to comment Share on other sites More sharing options...
Steve in MA Posted June 16, 2016 Author Report Share Posted June 16, 2016 I've resolved my issue, and discovered a bug. I've found "c:\windows\syswow64\smartdeploy\clientservice.xml.console" as the file where the console name/address is located. If I use an IP address, communication is fine. If I use my machine name, it is not actually entered into the file at ConsoleIPAddress. Further testing shows if I use fully letter based names such as "tester", or "doiwork", the information will show up, however, we have a wide usage of underscores in our naming convention. If I set the console to be "testmachine", it will appear in this file, but if I set it to be "test_machine", it will not, thereby not communicating. On my workstation, I do use an underscore in the name. I have not done any further testing to see if it is just an underscore or if there are other concerns like hyphens. In our case, most likely we would have to host this on a server for central use of multiple people (helpdesk, etc), and it wouldn't be a problem, but I will potentially have to hard code my IP to insure that this works, or change my workstation name to remove the "_" Link to comment Share on other sites More sharing options...
SmartDeploySupport Posted June 16, 2016 Report Share Posted June 16, 2016 Steve, Interesting. Thanks for bringing this to our attention. We will discuss this in our daily dev meeting today and do some local testing. Thanks again for letting us know, SmartDeploy Support Link to comment Share on other sites More sharing options...
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