How to manually remove a windows printer driver

      1. Examine print driver properties, record file names.
2. Stop print spooler
3. Goto registry: HKLM\System\CurrentControlSet\Control\Print\Environments\WindowsNT 4. X86\Drivers\Version-X\<printer driver name> Version-x where x is 1,2,3. (3 is for windows 2000 and higher drivers.). Printer driver name is the literal name of the printer driver
4. Delete that Key.
5. Go to %systemroot%\system32\spool\drivers\platform. Where platform is going to be “intel” and the subfolder is “w32x86” and the subfolder “3” for windows 2000 and higher drivers.
6. Delete the recorded files.
7. Start the print spooler service.

Complete list of Entourage 2004 port requirements

Ports in Bold indicate SSL setup on the exchange server and on LDAP. Otherwise use ports un-bolded.

1.       80/443 to Exchange (mailbox synch, public folder access, free/busy info, shared folder access, quota management)

2.       53/389/636/3268/3269 to Global Catalog domain controller (Setup assistant, GAL, Password expiration notice)

3.       135 to Exchange (delegate management)

Debian SNMP daemon is not listening on addresses other than the loopback.

By default, with sarge/etch at least, the SNMP daemon will only listen on the loop back.
Instructions to fix:
Under /etc/default/snmpd there is a config file, edit it.
Find the line that looks like:
SNMPDOPTS='-Lsd -Lf /var/log/snmpd.log -u snmp -I -smux –p /var/run/snmpd.pid 127.0.0.1'
And change it to read:
SNMPDOPTS='-Lsd -Lf /var/log/snmpd.log -u snmp -I -smux –p /var/run/snmpd.pid'
Then restart the SNMP daemon.

Remotely enable Remote Desktop Protocol to a target server.

Requirements: Local admin or domain admin privilege on the target server.
Use the registry editor to connect to the remote registry of the target server.
Find the following key:
"HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server"
Set the key fDenyTSConnection, where 1=disabled, and 0=enabled.
Then make sure the user account for connecting is in the local  remote desktop users group on the target server and you can connect in.

Consistent Autoenrollment errors on a Domain Controller after every reboot.

If the enterprise CA is also one of the domain controllers, you need to add the "Domain Controllers" group to the domain local group "CERTSVC_DCOM_ACCESS", and this will correct the issue.
This group was created during the last server 2003 service pack, domain users and domain computers are automatically in the group, however domain controllers are not.

Manually uninstalling Intelligent Message Filter v1 prior to exchange 2003 service pack 2

When installing Exchange Server 2003 Service Pack 2 to an existing Service Pack 1 system, the service pack can fail if the update for the Intelligent Message Filter v1 is already installed.
To manually remove Intelligent Message Filter v1

1.     Stop all Exchange services (Information Store, System Attendant, SMTP, and Exchange-aware antivirus services).

2.     Rename the MSCFV1 folder in X:\Program Files\Exchsrvr\bin, where X is the drive letter where Exchange Server is installed.

3.     Rename the ContentFilter.dll file in X:\Program Files\Exchsrvr\bin\, where X is the drive letter where Exchange Server is installed.

4.     Open regedit and export the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange key.

5.     Delete the ContentFilterVersion sub key from the registry.

6.     Restart the server. You should now be able to install Exchange Server 2003 SP2 without errors.