Initializing the root folders to display

Microsoft has changed the way the Office suite handles file and folder information in newer versions of Office.

If you are working on a domain joined workstation, this is more likely to happen in any of the Office 2007 Applications:

Whenever you try to save a document or open a document with the office applications, the above pop-upwill open and it will take some time to get the control back. This is mainly due to disconnected network drives. The mapped drives might not be available anymore or you don’t have proper permissions.

FIX: Disconnect the network drives and reconnect them with the proper credentials and then the pop-up will disappear.

If your network drives are mapped when you login using a logon script, then first disconnect all the network drives and go to \\<domainservername>\SYSVOL\<domain>\scripts\<yourname>.bat and execute it. All the drives will be mapped if you they are available and authenticated.

Replace <> tags with your environment names.

eg: \\ad01\SYSVOL\contoso\scripts\technobuff.bat

what is an .msu file?

A file with .msu extension is used to deliver Windows updates (security updates, critical updates, updates, update rollups or hotfixes) or downloadable setup packages to the Windows Vista and in Windows Server 2008 system.

msu stands for Microsoft Update Standalone Package. These files are associated with the Windows Update Stand-alone Installer (Wusa.exe) in Windows Vista and in Windows Server 2008. The Wusa.exe file is in the %windir%\System32 folder. The Windows Update Stand-alone Installer uses the Windows Update Agent API to install update packages.

An .msu file contains the following contents:

• Windows Update metadata
  This metadata describes each update package that the .msu file contains.
• One or more .cab files
  Each .cab file represents one update.
• An .xml file
  This .xml file describes the .msu update package. Wusa.exe uses the .xml file when you perform an unattended installation of the update by using the Package Manager tool (Pkgmgr.exe).
• A properties file
  This file contains string properties that Wusa.exe uses. For example, this file contains the name of the associated article in the Microsoft Knowledge Base.

To install an .msu update package, run Wusa.exe together with the full path of the file. For example, if the Windows6.0-KB952876-x86.msu file is in the C:\Temp folder, type the following command at a command prompt to install the update package:

wusa.exe C:\Temp\Windows6.0-KB952876-x86.msu

You can also double-click the .msu file to install the update package.

You can’t open the .msu file on a computer that is not running Windows Vista or Windows Server 2008. You cannot extract or view the MSU’s contents. To resolve this issue, use the Windows Vista Expand command to extract and to view the files in an MSU.
expand -f:* “C:\934307\Windows6.0-KB952876-x86.msu” %TEMP%

Then, you type the following command at a command prompt:

pkgmgr.exe /n:%TEMP%\Windows6.0-KB952876-x86.xml

The terminal server has exceeded the maximum number of allowed connections

When a user tries to connect to a machine using Remote Desktop connection, they might come across this error message.

“The terminal server has exceeded the maximum number of allowed connections“

This is because Windows Server only allows two connections through RDP, and you’ve either got two people already logged on to that machine, or you’ve got disconnected sessions that still thinks they are active. If a user simply closes the remote desktop window when they’re finished, that user will still remain logged on, unless there is a time out configured in Terminal Services Configuration as follows

Terminal Services Configuration

If the Session time out is not configured, or the logged on users are not available, you wont be able to logon to the machine. To overcome this limitation, follow the steps as below.

open a command prompt or type in the RUN prompt

mstsc /v:[00.00.00.00/SERVERNAME] /f -console

eg: mstsc /v:192.168.1.10 /f -console
mstsc /v:ADSURF /f -console

This will connect to the physical console session on the server (also known as “session zero”). You will then be prompted with the login box and provide the administrator details. Then you will be connected to the Console Session on the server. Now you can reset the disconnected user sessions from Terminal Services Manager. Please note that if you get disconnected from this console session, you will  have to go physically to the machine.

More info on mstsc at Technet

UPDATE:
If you have Windows Vista with SP1 or Server 2008, use the following syntax:

mstsc /admin

If you use the old switch “/console”, it will just ignore that and proceed connecting. In Windows Server 2008, the /console switch doesn’t exist anymore because “session 0″ is a non-interactive session that is reserved for services. Difference between admin and console swtich are here.

Another workaround:

You can also query the sessions on the remote machine as an administrator of that machine. Open a command prompt as a domain administrator that the remote machine is set to or map a drive of that remote machine.

Then in the command prompt, type as below:

query session /server:servername

Replace servername with the remote machine name or IP address.

Now we have the information of all the users/sessions that are active/disconnected on the remote machine. We can now reset one of the session with the following command.

reset session [ID] /server:servername

Replace [ID] with the number from the prevoius output and servername with the remote machine name or IP address. This will reset the session and now you can login using Remote Desktop connection.

Terminal Services Configuration

Greased Lightbox

→←+-↻

Loading image

Click anywhere to cancel

Image unavailable