Search results for query: *

Why not set up a trust and then log on to the correct domain? i.e. a two way trust You can then have your machine in D1 and log on to the D2 domain when necessary. "Be Excellent To Each Other" :-)

Does the user have any sort of file synchronisation from the client? Could possibly be removing stuff off line and then synching that removal... "Be Excellent To Each Other" :-)

If you have no roaming profile at the moment the user will get their local one, when they log off this profile will be written back as the roaming one (in theory!) and then when they log back on the roaming profile will be used (as per settings in the user account) "Be Excellent To Each Other" :-)

I'm not sure you can, not without using a third party tool of some description. "Be Excellent To Each Other" :-)

This may sound stupid, but have you emptied the recyle bin? "Be Excellent To Each Other" :-)

That'll work, for some reason I had it stuck in my head that there was more than 1... "Be Excellent To Each Other" :-)

Take a look at KB327709, has some info on same level security "Be Excellent To Each Other" :-)

Had a similar problem, was down to SP level of the CD image and riprep image, ensure you are using the same level SP on all machines involved (include the server in that!) "Be Excellent To Each Other" :-)

Ok here is my little recommendation:- 1. Do not seize, instead transfer the roles, this is far less critical (seizing assumes you cannot talk to the original role machine) 2. It is good practice not to have all 5 roles on a single box (ADCheck is a tool that when run will warn against this) 3...

I havent come across the ingroup.exe tool, I have used the ifmember.exe on multiple platforms. This is in the reskit. Remember: Backups save jobs!!! ;-)

I use the GPMC available from Microsoft as a download. Good tool, though I have very few policies and saved them as HTML. Enjoy... Remember: Backups save jobs!!! ;-)

Im actually talking about clicking on start\shutdown locally. I'm tempted to introduce clearing the pagefile as that will introduce a delay anyway. Remember: Backups save jobs!!! ;-)

Anyone know of a way to slow down (yes I did say slow down!) the shutdown time on NT? I've looked at all the bits concerning killing processes etc and they aren't really what I am looking for. I simply need to delay the time out, it has to do with roaming profiles not being written back before...

Your not running CPU intensive 3d graphical screen savers on your servers are you? Remember: Backups save jobs!!! ;-)

Actively use the 50/50 rule (a slight amenedment on the 80/20 rule!) and use an exclusion range rather than splitting the scope up. Remember: Backups save jobs!!! ;-)

run NET HELP USER from a cmd prompt...this will tell you all you need to know... Remember: Backups save jobs!!! ;-)

If all you are doing is excluding the addresses in question then you wont need to stop either DHCP scope. If you are physically splitting the scope into 2 smaller scopes then yes when you are doing this the DHCP scope would need to be deactivated. Remember: Backups save jobs!!! ;-)

It is available in W2K, on checking an NT4 box the option appears to be greyed out so this option probably only applies to W2K...though I am not 100% sure... The option is located under the properties of the server itself within DHCP manager (am using Windows XP tools to manage). Remember...

Is the BDC the workstations authenticate to a NT4 or W2K DC ? Are the workstations in the same domain as the NT4 BDC onsite? Remember: Backups save jobs!!! ;-)

Here is a good one...rename the administrator account and then create a seperate account called administrator, won't stop the determined hacker but will annoy the hell out of them when they realise they have hacked the password on a useless account :-) Remember: Backups save jobs!!! ;-)