
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-10-2016 03:02 PM
- Labels:
-
General Discussion

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-23-2016 11:01 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-23-2016 01:38 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-23-2016 08:39 AM
servicedesk wrote:
What about a deployment that creates scheduled task to run at the start up?...
You mean without the use of Lansweeper?
Is a possible solution and we use it in a pre Lansweeper time. But now we have Lansweeper running and now we explore the boundaries and limitations of Lansweeper.
Some status update:
We have modify som packages and ad a simple step to prevent a installation if a user logged on.
query user | findstr /i /l "rdp console"
On the historical startup script (kixtart) we trigger a scan on system startup and if the startup script has done his normal work the script check if a deployment running
tasklist | findstr /i /c:"RemoteDeployment_"
In this case the script show a progress indicator and prevent a user logon.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-14-2016 03:41 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-14-2016 03:33 PM

tasklist | findstr /i /c:"RemoteDeployment_"
say there is a process RemoteDeployment_x64.exe or RemoteDeployment_x86.exe the deployment is running and i wait in the system startup script until the process is not longer listed or a timeout is reached.
What I lack is recognize whether the scan has been performed or not.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-14-2016 01:33 PM
If the deployment take 5 minutes, and the user logs in after 20 seconds, there is nothing you can do about that. That's nothing to do with Lansweeper or the client.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-14-2016 12:15 PM

start /w \\%LSServer%\%LSShare%\lsclient.exe %LSServer%but the process don't want wait of the works end.


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-11-2016 01:29 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-10-2016 05:43 PM
