Search results for query: *

You can use the Local Security Policy | Security Settings | Local Policy | Audit Policy to set up logging. There are various options in here but if you tick the boxes for Success & Failure under the Audit Logon Events option your successful & failed logon attempts will show up in your Security log.

Take a look at the following from Microsoft: http://support.microsoft.com/default.aspx?scid=kb;en-us;248993 I had the same problem on a couple of servers and fixed it by modifying the registry as described. Good luck.

Just a thought but have you assigned your account User permissions on the mailboxes in question? You won't be able to open them otherwise, although you will be able to administer them. Good luck!

Yeah Zelandakh that does make sense. The only reason I didn't say that is because I have the Backup Operators group in there by default and thought that may be required for something. Obviously don't want any normal users to be able to shutdown the server!!

Go to Local Security Policy | User Rights Assignment and the option Shut Down the System, and make sure the Users group is not there. They will still get the Shut Down option on the menu but once they click Shut Down, they will only be given the option to Disconnect or Log off. (If you find a...

I usually just take a copy of usrmgr.exe from the NT server and paste it somewhere on the Windows XP machine. It still picks up all the same accounts. Is this what you're looking for or am I missing the point??!

Thanks - we are using WINS which is set up correctly, but not DNS since it is part of an NT 4 domain. Wouldn't that affect more than just the menus anyway? I should add that we are running plenty of Windows 2000 servers with no issues. Thanks.

Is anyone else experiencing a problem with slow menus on Win 2003? I have a new installation which seems fine in other areas - the general speed of the server is fine and accessing files/folders through windows explorer is fast enough, but when accessing the program menu or other menus that have...

Sorry! Forgot to add this link: http://support.microsoft.com/default.aspx?scid=kb;en-us;829246&Product=win2000

Clearing the event log should also do the trick.

I'm not sure if you can turn this option off but as a workaround you could try a button pushing utility such as 'Push the Freakin' Button'. This is freeware and it works for me. Take a look: http://www.bobos.demon.co.uk/par/PTFB.htm

Are you using SP4? If so I had the same problem and apparently there is a known issue with event logs corrupting. See the following from Microsoft: http://support.microsoft.com/default.aspx?scid=kb;en-us;829246&Product=win2000 The way I fixed it was just to clear the event logs and then they...

Have just found the way to do this for all users. First do as GaZZaW suggests for admin user logged on to server, and then go to Group Policy | Local Computer Policy | Administrative Templates | Windows Components | Internet Explorer and set "Security Zones: Use only machine settings&quot...

Yes they do have a host file, I think it is called Hosts or Hosts1 and is located in the root. Sorry, can't be more specific as I'm a Windows user but I have used this before!

Take a look at the following from the CA website. Not sure if it is exactly the same problem but I've had the E8604 error a couple of times and this fixed it. http://support.ca.com/techbases/asnt/NASNT707.html

Make sure you have entered a password and are not using a blank one. Sounds crazy but I have seen problems with this in the past. Good luck.

Make sure your server doesn't have more than 4GB RAM as NT will not install if it does. See the following for more info: http://support.microsoft.com/default.aspx?scid=kb;en-us;160392 Good luck.

I'm fairly sure it will just skip it until next time it reboots, but retain the username & password. Probably worth running a couple of tests to be sure though!

Do you mean when you reboot the server? No I don't think it will retain username & password if you just enter net use into a dos prompt. That's why I thought you could maybe add the info into a small batch file and get it to run on server startup or something. It's not something I've tried...

...a batch file that you put in startup or somewhere with the net use command. The syntax would be something like: net use V: \\%clientname%\C$ /user:*username* *password* where username and password are of the account that you use to connect to the other machines. This will prevent you being...