Microsoft .NET – Re-establishing connection with the server

Reading Time: < 1 minute

Usually, .NET installs go through with out issue, but this is one to watch out for.

You run the dotnetfx35.exe file but the install hangs on ‘Downloading – Re-establishing connection with the server’ (Click image below to enlarge)

This worked for me:

1) If you’re installing Microsoft .NET Framework 3.5 SP1, download the full package from http://download.microsoft.com/download/2/0/e/20e90413-712f-438c-988e-fdaa79a8ac3d/dotnetfx35.exe

2) Save to a location on your machine. For example you save to c:\net35SP1

3) Open a command prompt and type the below:

c:\net35SP1\dotnetfx35.exe /x c:\net35SP1

3) Press enter. The above command will extract the install to c:\net35SP1

4) Run the setup file from the folder you extracted to and it should go through without the above re-establishing connection issue.

Remote Desktop cannot connect to the remote computer because the authentication certificate

Reading Time: < 1 minute

When you remote desktop to a server, you receive the below error:

Error:
Remote Desktop cannot connect to the remote computer because the authentication certificate received from the remote computer is expired or invalid.
In some cases, this error might also be caused by a large time discrepancy between the client and server computers.

A common issues is date and time settings and the answer is actually within the error message.

Here it is:
In some cases, this error might also be caused by a large time discrepancy between the client and server computers.

So a possible resolution is:

Check both the date and time on the client machine. The time may be correct, but the date incorrect, so check both.

Controlling permissions to applications available via redirected desktop or start menu

Reading Time: 2 minutes

I have seen lots of environments where administrators have setup several start menu or desktop redirected folders for different departments with an organisation.

For example:
Sage Payroll should only be available for the Payroll department, so therefore a redirected start menu folder is setup for the payroll department. Another redirected start menu folder may be setup for the I.T department and so on. At the end you may have several redirected start menu and desktop folders which can look messy and become difficult to manage.

Microsoft do have a tool available which will make your life much easier and allow you to use one start menu or desktop folder for all users. You can make shortcuts available to users depending on what security groups they are part of. So you have one redirected start menu folder for all users but only make apps available which they need to use, and this is all controlled by Security Groups.

The tool is Share and Storage Management which is part of Windows Server 2008 and replaces File Server Management tool in Windows Server 2003.

To add the feature to a Windows 2008 server:

1. Start the Server Manager
2. Click Roles
3. Click Add Roles
4. Select File Services and click the Next button
5. Select File Server Resource Manager
6. Decide which volumes you would like to monitor and configure the rest as required
7. When done, the File Server Resource Manager and the Share and Storage Management tools are installed

To configure the feature

1. Access Share and Storage Management tools via programs, administrative tools
2. Right click on the share, for example startmenu if you have one
3. Click Properties
4. Click the advanced button
5. Click ‘Enable Access-Based enumeration’ and click OK
6. Click the permissions tab and setup share permissions and NTFS permission as required. If its for a redirected start or desktop folder, you may want to allow users
read only access.
7. Click OK when done
8. Now access your redirected start menu folder where ever it is setup, right click on a shortcut, for example Sage Payroll and add the Sage Security Group to the security tab. The result is, the Sage Payroll application shortcut
will only be visible to users within the Sage Security Group.

Locate Windows Update server name within registry

Reading Time: < 1 minute

If you need to know where your client machine points to for it’s windows updates via registry, follow below instructions.

Please note:
Modifying the Windows registry can be dangerous. Incorrectly modifying the registry can destroy your operating system, applications or data. I therefore highly recommend that you perform a full system backup prior to attempting any of the techniques on this website.

1) Launch registry
2) Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
3) The Windows Update server name can be located within the registry name WUServer

Check for newer versions of stored pages – group policy

Reading Time: < 1 minute

1) Edit the policy you wish to apply the change to
2) Expand User COnfiguration
3) Expand Windows Settings
4) Right click ‘Internet Explorer Maintenance’ and click preference mode. (Needs to be enabled)
5) Click Advanced
6) Double click Corporate Settings
7) Click Temporary Internet Files (Users)
8.) Drop down and select as required
9) Click OK