Will Lansweeper still push data for both computers to the Lansweeper database once we get lspush. We also have two machines that login with the same user name. That specific functionality will not be able to be performed by LsAgent. Is there someway to prove that when the user on this computer logs onto the the network, that startup.cmd is truly running? Lansweeper Employee Options 09-19-2018 12:12 PM LsAgent is superior to almost all ways to LsPush, except that due to the way that LsPush can be called, it can be added to a logonscript, which allows for more accurate logon tracking. However Lansweeper still reports that this problem machine has still "not scanned". When this particular machine is turned on and the user logs into the domain, I figured Lansweeper would see the results of running startup.cmd and lspush.exe via the netlogon files. Now under users and computers on the same 2008R2 server, I select a domain user who is not being scanned by Lansweeper and under their profile in the Logon Script field I enter startup.cmd just as is shown on page 34 of the Lansweeper documentation. So to me this proves the cmd and netlogon are setup and ready. scan your computers with the LsPush scanning agent instead. When I manually run startup.cmd within the netlogon share located on my 2008R2 server where Lansweeper is running, I see the command line dialog box open, the cmd runs and I see that Lansweeper verifies & records that the 2008R2 server has just been "seen". Regardless of which option you choose, Lansweeper will pull most Windows computer data from. From Lansweeper version 6.0.100. I have both startup.cmd and lspush.exe located in my netlogon share that is part of my 2008R2 Server. I have a working startup.cmd that looks exactly like the cmd on the top of page 35 in the Lansweeper documenation. I too am using the same version number of LSPUSH.EXE
0 Comments
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |