Search results for query: *

Yes i know that, however as i said i have a number of printing issues. Installation of MPSE300W2KR02 will resolve some of those issues, however installation of it seems to be causing me a bigger problem then without the patch.

Also depends on the server. Some servers will allow you to hot swap the drive out, so its just a matter pulling out the old one and putting in the new one. Then using the servers array software rebuilding it.

Mainly because Im having various printing issues and other small issues with certain apps not running properly. As the MPSE300W2KR02 is the cumulative patch of all the previous hotfixes and you can no longer get the individual hotfixes from the Citrix site, not much choice really! But guess...

Just tried installing the citrix Hotfix MPSE300W2KR02 and after it was installed, noone could connect to the server from remote sites if connecting from a Windows NT machine. (Win 2000 machines were fine) Soon as I uninstall it, they all connect fine again. Does anyone know of any workarounds...

try it with dword in lower case. Might sound silly but I think the case matters!!!

I've had something similar and it was down to registry rights. Look at the following article http://support.microsoft.com/default.aspx?scid=kb;en-us;329888 Also check the permissions on the registry and make sure everyone has rights to modify the key as this is what i had to do.

You can edit the .reg file (using notepad) and choose what keys you want in there. Delete all the bits you dont need. regedit would then merge the file into the registry overwriting the keys you want or adding new ones. (it wont delete existing keys) in your case all you should need is...

Are you actually promoting the PC to a Domain Controller? Also you might want to replicate DNS to the PC as well as you might have problems if on you lose your DNS server.

Create a .reg file with the registry settings (best way is to use regedit to export the registry key to a file) In the login scripts just add regedit /s <reg file> the /s switch runs it silently so users dont know. As long as the reg file is in the NETLOGON share it should pick it up no problem

You can always put it into the login scripts as an alternative.

Think a better approach could be to stop users being part of the local admins group. That way they cannot remove the domain admins from the local administrators group. There is normally very little reason why users would need local admin rights.

Another tool you can use is showacls.exe which is on the 2000 resource kit. I have found this just as effective for getting ACL's of directories. Syntax is simply showacls /s <path> You can simply pipe the results to a txt file so showacls /s D: > permissions.txt It will list all...

Forgot to add you might want to add the following changes to GPO Computer Configuration\administrative templates\system\logon Enable delete cached copies of roaming profiles ( or else they will just build up) Add administrators security group to roaming user profiles. (Or else if you need...

I dont think by default it will create the folder. However once the user logs via citrix it will create the profile folder then.

I have an organisation with a number of sites most with just one server in it. One of the servers has died and so effectively we have no server on that site. The server which has died is a 5.5 server. As we are in the process of migrating to 2000 it has been decided rather then rebuild the NT...

First of all find out what is filling up the eventlog. Might be trivial things such as printing. You can always stop these things writing events to the Event log. Also you can change the event log setting to Overwrite events as needed. This will start to overwrite the older events once the...

try it regedit /S <reg_file>

regedit.exe <reg.file> /S the /s switch does it silently.

With windows 2000 you only get a professional version for user PC's. As for which is better XP or 2000 i think its personal choice. Personally i cant stand XP since the release of SP2 on it.

I would say purely down to the server specs and the apps you got running on it. I have some dodgy 16 bit apps published which occasionally crash and just mess up the whole server so I've set the servers which publish those to reboot every night. For my other servers i get them to reboot over...