Disable Firefox Auto Update for Terminal Servers

Disable the auto-update feature in Firefox.

I accomplished this by first creating a file called mozilla.cfg in the C:\Program Files\Mozilla Firefox directory with the following contents:

// Disable Auto Updates
lockPref(”app.update.enabled”, false);
lockPref(”extensions.update.enabled”, false);

Those instruct Firefox to disable the auto update for the browser itself AND any add-in extensions.

Also you must edit C:\Program Files\Mozilla Firefox\greprefs edit the file all.js and add this to the bottom:

// Process mozilla.cfg in FireFox root directory.
pref(”general.config.obscure_value”, 0);
pref(”general.config.filename”, “mozilla.cfg”);

Without that last piece, Firefox won’t process the mozilla.cfg you created.

No reboot needed, and hopefully you’ll never run into this again.

Roaming Profile Review

By default in Windows 2003, a roaming profile only assigns permissions to the named user and the local system account, the administrators do not have permissions to this folder, and there is a security check before loading the folder that indeed only those two accounts have access to that profile. Additionally the user is the owner of the folder and all sub-folders/content.

When troubleshooting profile problems, you will need to click on the advanced tab under security and take ownership of the folder, which you can do as a local administrator, however once you do this the profile may break. After that, you will typically assign the administrator group full access to the folder.

Once you are done, please be sure to remove the administrator under security, as well as change the ownership of the folder and sub-folders/content back to the named user. Otherwise you may experience problems with the profile.

This default behavior can be changed via Group Policy or via the Registry, which will permit additional users, and bypass the security check, but it is not recommended.

This is an except and overview of the detailed article at: http://technet.microsoft.com/en-us/library/cc757013(WS.10).aspx

70-290 Concepts: Networking/Terminal Services

graduation·          Under Windows Server 2003, the default share permissions are Everyone: Allow Read (previously Full Control in Server 2000)

·          Under Windows Server 2003, the default NTFS permissions are Administrator/System/Owner: Full Control; Users: Allow Modify


·          NTFS permissions are cumulative, with deny always overrides; share permissions + NTFS = lowest takes precedent.

·          Share folders cannot be renamed; share folders with a postfix of $ will be hidden in Network Places.

·          Quotas: admin @ unlimited; assigned per-user/per-drive. Not assignable to groups; based on file size regardless of disk compression

·          Shadow copies automatically backup copies of shared folders at scheduled times, must be NTFS formatted, setup per volume, must have client software installed and accessed via UNC (\\server\share)

·          Terminal Services (TS) Licensing: Remote Administration Mode: 2 concurrent users max; Application Server: need per client license for every client

·          TS management, permitting to view/connect/disconnect/logoff/send message/remote control

·          TS configuration permitting control over Active Desktop/temp files/encryption level/local resources/etc.

·          Should use tsshutdn.exe instead of shutdown since it will notify remote users of the restart.

·          Control of remote desktop on server via right-click My Computer > Properties > Remote

·          The print spooler service loads files to memory for printing, if there is a problem restart the service.

·          Terminal Services Licensing server:

o    Terminal Servers first check their registry for a possible pointer to a license server; then they query

o    Enterprise License Server which can run on a DC or member servers; registered existence in AD for the local site only; then they query

o    Domain Licensing Server: only exists on domain controllers


RDP Multi-monitor support

dual lcd displaysBasic dual monitor support is available under the Remote Desktop Protocol / Terminal Services. You must be running the RDP Client v6 or higher. You must run the command from either the RUN or CMD line interfaces. For frequent use you could always create a batch script which you can run from the desktop.

command:> Mstsc /span


For more information, see: http://www.microsoft.com/downloads/details.aspx?FamilyId=26F11F0C-0D18-4306-ABCF-D4F18C8F5DF9&displaylang=en

Powered by WordPress.com.

Up ↑