So I have a weird question. We are getting ready to integrate a new company we purchased onto our network. Currently their network is connected to use but they are still on their old companies domain with no trusts to our domain. We want to get a snapshot of their workstations so we can know if their computers are up to snuff for our systems or do they need to be replaced. So of course the best tool to gather this information is LANDesk, but is there a way to install the client on these machines without them being part of the same domain as LDMS? For kicks and giggles we already tried to send the client from LDMS and it failed. Is there another way to get them reporting in LANDesk? In the end the computers will be converted to our domain and their old one will be eliminated but the information is needed before we do that.
The simple way is to right click on your agent, create a self contained executable agent and run the .exe on the system.
Once the client is installed, it does not matter if the system is in your AD or not. (For most stuff, including patching, access to dfs or package shares might matter)
So as long as the computer can see the LANDesk server on the netwrok if we do the install from a self contained executable it will communicate the inventory back?
James is exactly right, a self contained executable will work.
Additionally you can add credentials from the other domain to your Global Scheduler service and then push them out. If they are workgroup computers this will most likely not work, because they default to some different security settings than domain computers do, but if they are on a domain you can add alternate credentials from their domain by going to Configure - Services on the Core server, then the Scheduler tab. From there you can click on Change Login and add their domain admin credentials under the Alternate Credentials box. Then you should be able to push the agent (assuming they have their firewall off, etc.).
I will give James' idea a try since it will be the easiest.
We recently did such a thing with an acquisition. What we did was ship a preferred server to the locations. Got local administrative account credentials. Did an unmanaged device discovery. Provided a device listing CSV for them to specify devices to load the agent (and which agent) on and used LDDiscover to get the needed agent loaded on devices. We did this for two remote locations and for about 650 nodes. It worked fine and we were able to immediately patch and distribute software.
You can always install a self contained .exe on one of them.
Or can add some domain credentails for the new domain to the scheduler tab.
1. Click on configure services from the LANDesk toolbar.
2.. Select the scheduler tab.
3. Click the "Change Login" button
4. add a domain admin account for the new domain under the "alternate credentials" section.
5. Restart the scheduler service.
6. Try to redeploy the agent to the computers on the new domain.
Note you can multiple accounts to this section. It will just go down the list and try every account you add until it finds one that it can use.
The ideas keep getting better and better...