
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-28-2005 08:12 PM
Good Morning,
I have Lansweeper on and working well. Our system operator has it setup as a startup script when the machine boots. However we've been getting alot of corrupt Windows 2000 profiles with it on. We turned the service off for a week and had no problems. We just turned it on today and started getting them again. Has anyone run into this? Also should we make it a login script and NOT a startup script. Can a regualr user run it when they login if they don't have admin privledges?
~Mike
I have Lansweeper on and working well. Our system operator has it setup as a startup script when the machine boots. However we've been getting alot of corrupt Windows 2000 profiles with it on. We turned the service off for a week and had no problems. We just turned it on today and started getting them again. Has anyone run into this? Also should we make it a login script and NOT a startup script. Can a regualr user run it when they login if they don't have admin privledges?
~Mike
Labels:
- Labels:
-
Archive
2 REPLIES 2

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-28-2005 08:38 PM
I think that's our problem then. I will have our systems guy make it a logon script and not a startup script. Thank you for your quick reply. 🙂
I'll keep you posted!
~Mike
I'll keep you posted!
~Mike

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-28-2005 08:27 PM
A regular user (logged into the domain) must run the lsclient.exe
You must use script located in the %logonserver%\netlogon folder
I have never heard of problems with corrupt profiles.
You must use script located in the %logonserver%\netlogon folder
I have never heard of problems with corrupt profiles.
