Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
M DRIVE LOCATION
- Thread starter GP
- Start date
Don't ever mess with drive M: or your entire exchange will be gone!
You can either reinstall and use another drive, or go through the steps of moving Echange to another disk, if you have one.
Marc
If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all. Please specify details.
Free Tip: The F1 Key does NOT destroy your PC!
You can either reinstall and use another drive, or go through the steps of moving Echange to another disk, if you have one.
Marc
If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all. Please specify details.
Free Tip: The F1 Key does NOT destroy your PC!
compgirlfhredi
Technical User
Three big issues with this script.
1) only deletes for the individual users session. You can put it into the logon script but the users can click on the close box to stop the script from running.
2) the script actually stops and then restarts the exchange services. So if it's in the logon script everytime a user logs on it makes the exchange server stop and then restart
3) User must have permission to start and stop services and mess with the registry. Not a big fan of that either.
"1) but the users can click on the close box to stop the script from running"
According to You can set up scripts to run when users log on or log off, or when the system starts up or shuts down. All scripts are Windows Scripting Host (WSH)-enabled. By default, Group Policy scripts that run in a command window (such as .bat or .cmd files) run hidden, and legacy scripts (those defined in the user object) are by default visible as they are processed (as was the case for Windows NT 4.0), although there is a Group Policy that allows this visibility to be changed. The policy for users is called Run logon scripts visible or Run logoff scripts visible, and is accessed in the User Configuration\Administrative Templates node, under System\Logon/Logoff. For computers, the policy is Run startup scripts visible and can be accessed in the Computer Configuration\Administrative Templates node, under System\Logon.
"2) everytime a user logs on it makes the exchance server stop and then restart"
Nothing to do about that, but you can limit it to once a day for each user, if you save a "dummy-file" to tell about it, and test the dummy-file, for last access. You have to use WSH, to append date/time.
"3) User must have permission to start and stop services"
I can't find it, but there must be a global policy to allow certain users access to stop and start services.
1) only deletes for the individual users session. You can put it into the logon script but the users can click on the close box to stop the script from running.
2) the script actually stops and then restarts the exchange services. So if it's in the logon script everytime a user logs on it makes the exchange server stop and then restart
3) User must have permission to start and stop services and mess with the registry. Not a big fan of that either.
"1) but the users can click on the close box to stop the script from running"
According to You can set up scripts to run when users log on or log off, or when the system starts up or shuts down. All scripts are Windows Scripting Host (WSH)-enabled. By default, Group Policy scripts that run in a command window (such as .bat or .cmd files) run hidden, and legacy scripts (those defined in the user object) are by default visible as they are processed (as was the case for Windows NT 4.0), although there is a Group Policy that allows this visibility to be changed. The policy for users is called Run logon scripts visible or Run logoff scripts visible, and is accessed in the User Configuration\Administrative Templates node, under System\Logon/Logoff. For computers, the policy is Run startup scripts visible and can be accessed in the Computer Configuration\Administrative Templates node, under System\Logon.
"2) everytime a user logs on it makes the exchance server stop and then restart"
Nothing to do about that, but you can limit it to once a day for each user, if you save a "dummy-file" to tell about it, and test the dummy-file, for last access. You have to use WSH, to append date/time.
"3) User must have permission to start and stop services"
I can't find it, but there must be a global policy to allow certain users access to stop and start services.
- Thread starter
- #6
See to move the data to another location.
A delicate operation! Make sure you have a fully checked backup before doing anything!
A delicate operation! Make sure you have a fully checked backup before doing anything!
- Status
Similar threads
- Locked
- Question
- Locked
- Question