Thursday 22 April 2010

XenApp 6 on Windows Server 2008 R1

Just in case there is any confusion on this matter, XenApp 6 will only install on Windows Server 2008 R2.

Trying to install on Windows Server 2008 gets you this nice specific error:

XenApp 6 on Windows Server 2008 R1

Some elements of the suite (License Server, EdgeSight, Web Interface) can be installed on Windows Server 2008 , but the main application will only install on 2008 R2, not 2008 R1 as it appears to now be called.

I only mention this as my web stats indicate this is something people are unclear on!  If you have Windows Server 2008 you’re restricted to XenApp 5. 

Upgrade.  Its worth it.

XenApp 6 servers in 20000 state - “An error occurred while making the requested connection”

A frequent error when establishing new farms and servers appears to be servers that have a bad licensing state.  The error you get when trying to launch applications is “An error occurred while making the requested connection”.

image

To test whether your farm is in this state, open an administrative command prompt on the problem server and run the command:

query farm /load

(or qfarm /load)

If the server you are launching from has a load of 20000, it is not licensed properly.

image

There are a few different reasons why this might happen.  This is not supposed to be a complete guide, but these are certainly things to try.  After each step, try rerunning the qfarm /load command.  If it goes down to zero, it looks like you have a licensed server.

  • Obvious things first – do you have a license server?!  This is not Terminal Services licensing, this has a grace period of 120 days.  Citrix licensing has no grace period as such (except when your license server fails after previously working, when you get about a month).  I posted a guide about creating a license server here.  Make sure you actually have a working server, that you have installed some real Citrix licenses to it, and that its a modern version.
  • When you are specifying the license server name, don’t fully qualify it – so say “servername”, not “servername.domain.com”
  • Look at the Dashboard on your licensing server and make sure the SA date is at least “2010.0317”. 
  • Just in case, sort your TS licensing out while you’re at it! 
    • Click Start,  Administrative Tools, Remote Desktop Services, RDS Host Configuration
    • Click Licensing Diagnosis
    • You should see a number of CALs available to clients and a nice green tick at the top of the screen.
    • Check the users you are testing with are actually in the Remote Desktop Users group on the server.
  • Check with telnet that you can connect to your license server from your Citrix server on port 27000 (or whatever you selected as the licensing port).  Could be a firewall issue on the licensing server.
  • Check you have enabled remote access on the server!!  Click Start, right click Computer, Click Remote Settings and make sure the second, less secure option is selected:

Windows 2008 r2 remote settings

  • Did you specify a license server on installation of the server you’re having trouble with?  If you did, check the server’s console (by plugging in a monitor, using ILO or looking on the VMware\XenServer console) to make sure it is not coming up with an error saying “Citrix XenApp cannot contact the license server…”.  You never know, you might have made a typo.
  • Check the value LSName at this registry location on the server:
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Licensing
  • Try running the XenApp Server Role Manager from the Start Menu on the server with the problem and disjoining the server from the farm, then rejoining, being very careful to get the licensing information right.
  • Try adding another server to the farm (I had one farm where nothing worked until a second server was added…), again getting the license bit right.  See if that server works.  If it does, its something you did on the first one.
  • Change the Load Evaluator your server is using to the Default one instead of Advanced (this was a problem in the Preview edition of XenApp 6, I don’t know if it is in the final release).
  • Set the licensing information for the farm in Group Policy…image
    • Open the Citrix Services Delivery Console
    • Expand the farm and click the Policies node
    • Assuming you only have the Unfiltered policy, select the computer tab, Unfiltered and click Edit.  If you have multiple policies, you might have to do this in all of them, depending on the make-up of your policy structure. 
    • Leave “Enable this policy” ticked and click next
    • Click Licensing on the left.  Click the Edit or Add button by the server host name and ports and enter the correct details.
    • Click Server Settings on the left hand side and click Add/Edit.  Select the product version you have licenses for in the drop down.  This should be the version you have licenses for on the license server. 
    • Click Save
    • You should now see the settings you just entered in the Summary section of Unfiltered. 
    • On the problem server, run gpupdate /force and reboot.
  • Try installing a new test license server in case the problem is there, especially if you have an old version installed.
  • Check the forums! 
    http://forums.citrix.com/thread.jspa?threadID=261939&start=0&tstart=0
    http://forums.citrix.com/thread.jspa?threadID=261884&tstart=0
    http://forums.citrix.com/thread.jspa?threadID=257331&tstart=0

Wednesday 21 April 2010

Windows 7 – Always show the Citrix offline plug-in (agent) icon in taskbar’s System Tray

Windows 7 has a change to the default functionality of the System Tray in that icons created there do not display by default.  Instead, users have to click a strange up arrow:

before change

You then get that white box appear and can click on your icons.  In this case the icons include that of the old PN Agent, the Offline Plug-in.  This extra mouse click is annoying, but the fact that less clued-up users won’t even know they can launch their Citrix apps from down there is an active problem.

It can be fixed per user by clicking Customise, finding Citrix XenApp in the list and changing the drop-down to “Show icon and notification”.

image

But that’s a bit rubbish since it can’t be set (that I know of…) by a script and is per user.  Nonetheless, that’s what I do on my PC.

To fix it for everyone your only option is to create a registry key which will force all System Tray icons to be visible on the Taskbar.  To do this, Click Start > Run (or press Win-r) and type regedit.

Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer

Right click Explorer, New > DWORD value called EnableAutoTray.  Leave its value as 0 (zero).  Log off and log back on and regardless of what you have previously set, all icons are now visible – including the Citrix agent.  Setting it to 1 will set it back to default for everyone, and removing the key lets you define it per user by putting it in HKCU.

after change

Here’s that registry key again:

image

Tuesday 20 April 2010

Installing EdgeSight For Load Testing for XenApp 6

The version of most software appears to have been incremented with the release of XenApp 6, and this includes EdgeSight For Load Testing (ESLT) which is now Build 3.6.1.24.

Oddly previous versions of ESLT appear to be a higher build number – the version I was testing XenApp 5 with was build 5.2 and it shipped with build 5.0. I assume they have reordered their build numbers! Please note that ESLT is a different program from EdgeSight – they can be installed on the same machine, but there is no reason as such to do so, and neither application requires the other to work.

  • Get a Windows Server 2008 or 2008 R2 server (I’ve tested XenApp 6 with an R1 server just fine).  You will need a XenApp License server set up too before you can use ESLT properly.  Make sure its got a lot of memory if its going to run a lot of sessions – I have found to launch more than 100 sessions meant more than 4gb of RAM and of course 64-bit OS if using Windows 2008.
  • Be aware that ESLT actually consists of 2 parts – the Launcher and the Controller.  You would only have one Controller usually to kick off the tests but you could have the Launcher software installed on several machines to actually launch sessions from lots of places.  This might be better for you if you don’t have a powerful server to run everything – personally I’ve always used one server for everything which is fine – if its up to it.
  • Uninstall any previous version of ESLT.
  • Get the folder “Load Testing Services” off the XenApp 6 DVD and copy it to your new Load Testing server.  Or download it from My Citrix.
  • Run EdgeSight for Load Testing.msi

image

  • Click next, agree to the EULA and click next again.
  • Click Custom (always click custom!)

image

  • Set all three components to install.  The “Web Interface XML Service” allows you to connect to applications more easily without messing about creating ICA files so is good to have.  It doesn’t actually use the Web Interface.
  • Enter a really good password

image

  • ESLT WI Support.msi is only needed if you are installing ESLT on a Web Interface server
  • After installation, you can make sure the essential service is started – its the Citrix EdgeSight Launcher Service and replaces the Launcher application from previous versions of ESLT

image

  • You can now run the LT Controller from the Start Menu

image

  • You will get a handy message about the changes you should make to your Citrix servers in order to be able to do Load Testing. These are important so don’t ignore them. You might well not want these settings on your live production servers!

image

  • To implement these settings, log on to your XenApp 6 servers and click Start, All Programs, Administrative Tools > Remote Desktop Services and click “Remote Desktop Session Host Configuration”
  • Right click ICA-TCP in the middle of the screen and click Properties. You should be able to follow the instructions above on the Sessions and Log on Settings tabs. So this on any server you will use for hosting Load Tested applications.
  • After the handy message about server settings, enter your password to get to the main interface.
  • The last step is to license it, or you will only have a 30 day 15 user license (which is not of much use). Click the Licenses menu and select License Server Configuration.

You are now ready to do load testing!  The next high level next steps are

  • Create usernames to perform the load testing – I would create as many users as you will want to create sessions rather than reuse the same username lots of times.  This also gives you the option to give them mailboxes etc later.  Make your life easy though and make their usernames the same except for an incrementing number on the end and keep the passwords the same too.
  • Create a new EdgeSight test and connect it to an application on your farm (using an ICA file is one easy way to do this)
  • Enter your usernames and passwords
  • Record a script for load testing an application.  Best practice is to have folders for the steps – a load section and a log off section with a folder in between set to “Iterate”.  This section can then repeat infinitely until ESLT starts logging users off.  If you don’t do this a long test will see constant logon/logoff activity which can cripple the test.
  • Enter figures for how to load the test.  Usually, this will consist of a “log on” period where all your users log in at a realistic rate, a middle period where load is at maximum (this is a good time to test logon times and application performance of an extra session by logging on manually) and a short log off period where the tests complete and log off again.
  • If you’re testing Office 2007, you can download very good sample scripts from here: http://support.citrix.com/article/CTX122568.  They’re worth looking at even if you don’t use them as they’re well done scripts.  They can be adapted to work in Office 2003 and Office 2010 as well.
  • Under Display > Counters set up connections to useful perfmon counters on the servers being monitored – such as
    \\servername\Processor(_Total)\% Processor Time
  • Run tests – this will spawn many windows on your desktop (only have one user logged on to the launcher server or they can appear on the wrong session).  Usually its best to right click the stack of windows and click “Show Windows Stacked” to display them nicely.
  • Record the results – screenshots of the “Monitor” section of Display are best though you can save reports.

Monday 19 April 2010

Streaming OpenOffice.org 3.2.0 in XenApp 6 (streamed to server)

Preparation – installing your environment

  • Before you can stream applications, you need a Streaming Profiler. This should be as close to the final environment as you can make it, so the same operating system, patches, and other applications. Best practice if you are going to Stream to Server is the Streaming Profiler should be the same hardware as the farm servers and a member of the farm (though certainly not used to host live apps). In this case, I am planning to stream to server so this is a Windows 2008 R2 server and a member of the farm. Install the Profiler from the XenApp DVD and make sure your Profiler does not have the streaming client (the XenApp Offline Plug-in) installed.
  • Ensure the Visual C++ redistributable 2008 is installed – if you are installing to a XenApp 6 Farm server, this should already be installed by the installation of XenApp.  The same versions of the Redistributable should be on your intended clients (in this case the farm servers) too.
  • Download the latest version from http://download.openoffice.org/. This guide is for v3.2.0
  • Run the executable and select a directory for the extracted installer files. Cancel the installation once this directory is complete and keep the newly created directory. You can discard the original downloaded file.
  • The Java Runtime Environment is now not a requirement for either XenApp or OpenOffice so you might want to avoid it entirely. If you want it, install it manually to the Profiler and your XenApp machines before you begin and make sure everything is the same version.  I’m going to manage without it.

Preparation – disabling the first-run wizard

cd \
“c:\program files (x86)\Openoffice.org 3\program\unopkg” add --shared c:\DisableFirstStartWzd_ooo32.oxt
pause

Preparation – changing default file formats

  • Since we’re not all using OpenOffice, you probably want your users to save in Microsoft Office format by default. This isn’t a very easy process and will need some preparation. I’ve adapted the instructions from here and here.
  • On another machine of the same operating system, install OpenOffice 3.2.0 using the same process below (only actually install it, not using the Streaming Profiler).
  • Browse to “C:\Program Files (x86)\OpenOffice.org3\Basis\share\registry\modules\org\openoffice\Setup”
  • First open Setup-Writer.xcu with WordPad (NOT notepad).  It might be more readable if you disable Word Wrap.
  • Find this line:
    <prop oor:name=”ooSetupFactoryDefaultFilter”>
  • Change the text of the line below it (there might be a few occurrences, do them all) to read:
    <value>MS Word 97</value>
  • Open “Setup-calc.xcu” and find the line :
    <prop oor:name="ooSetupFactoryDefaultFilter">
  • Change the line after to read:
    <value>MS Excel 97</value>
  • Open “Setup-impress.xcu” and find the line:
    <prop oor:name="ooSetupFactoryDefaultFilter">
  • Change the line after to read:
    <value>MS PowerPoint 97</value>
  • Copy the three files you just created to the server you are profiling from so you can later add them to the stream

Creating the Streamed Profile

  • Click Start > All Programs > Citrix > Streaming Profiler > Streaming Profiler
  • Click New Profile

image

  • Click next
  • Give it a name (you can change this later). Click Next.
  • Do not enable User Updates and click Next.
  • Click Next past the linked profiles page (again, you can change this later).
  • On the list of Target Operating Systems you should see just Windows Server 2008 R2 selected. This is fine if you are streaming to server.

image

  • The only other OS that would probably work if you selected it now and tried to stream to a client on it later is Windows 7 64-bit, but there is no real point doing this. Click Next.
  • Select Advanced Install

image

  • Select “Run Install Program or command line script”

image

  • Click browse and find the setup.msi for OpenOffice in the folder you extracted. Click Next and Launch Installer.
  • Enter a generic User Name and Company and click next
  • Click Custom and next.
  • Deselect any main features you don’t need (in the screenshot I’ve disabled Base and Math as I don’t want my users messing about with these). Expand Optional Components and deselect On-line Update, Windows Explorer Extensions and Quickstarter at least.

image

  • Click next and clear the box to create a Start Link on Desktop.
  • Click Install and watch installation complete. Click Finish to return to the profiler.
  • Click Next.
  • Select Perform Additional Installations and click Next
  • Click Select Files and Folders
  • Copy your downloaded oxt file and the batch file you made to from your PC to the C: drive in the stream

image

  • Also find the setup-calc.xcu, setup-writer.xcu and setup-impress.xcu you may have created earlier to deal with default file formats not being Microsoft compatible. Copy them into the profile as well, into:
    C:\Program Files (x86)\OpenOffice.org 3\Basis\share\registry\modules\org\openoffice\Setup
    These should overwrite files and be newer and larger.
  • Click Next to perform additional installations again.
  • Select the first option again, to execute a program.
  • Enter the name of your batch file in the first text box and click Next

image

  • Click Launch Installer. You should see it successfully install the OXT and pause.

image

  • Click Next and select Finish Installations
  • You should now see a list of the main applications that you allowed at installation:

image

  • Select one and click Run. It should run without a first run wizard and have the expected default file format.
  • Click Next, Next, Next and Finish. After a few seconds it should finish building.
  • You should now see a screen with your new profile and some expandable folders beneath it.  Note the asterisk after the file name at the very top, indicating it is not saved yet. You can make lots of changes to the stream here by right clicking the new profile and clicking Properties. These include adding pre and post launch scripts and linking other profiles. When you are happy, save the profile to a file share. Enter the path of your profiles file share in the top box and it will create the subfolder for you. Click Save. This will take up about 400mb of space.  If you make changes and re-save, it will take another 400mb!
  • You are finished with the Profiler now.

Publishing your application

  • Open the Citrix Delivery Services Console (DSC) on a farm server with the Management Tools
  • Connect to the farm
  • Right click Applications and click Publish Application
  • Click Next and give it a display name – For example Word Processor

image

  • Select Application, Accessed from a server and Streamed to Server:

image

  • Click Next.
  • Click Browse to find your profile and select it. You should be able to select the application you want from the drop down:

image

  • Click Add to include servers to host the application.
  • Click Next to add users to get the application.
  • Finish the wizard, adding folders as required.
  • On a client in the name of a user who should see the application, do an application refresh and run the app.
  • Check the first run wizard does not run. Click File, Save As and check that the file format is Microsoft:

image

  • Repeat the process for Calc, Impress and the other OpenOffice applications as needed.

Friday 16 April 2010

Citric online plug-in – changing the Server URL breaks shortcuts

imageI’ve had a strange bug reported by one of my users when I changed the Server URL her PN Agent (sorry, online plug-in!) used to connect to the farm.  She had dragged lots of shortcuts from her Start Menu to her desktop for Word, Excel, etc and now none of them worked – they came up with “The requested resource has been removed from the server”.

Which it hadn’t.

Anyway, the new and old Server URL went to the same Web Interface server and connected to the same farms, just with different options – after looking a bit closer though the capitalisation I’d given the farm names in “Server Farms” under the different Web Services sites were slightly different – same letters, just different capitals.  I made them the same and the old shortcuts all started working again.  I then went through every Web Interface site and made sure they were all the same! 

Yet another picky “feature” of Citrix…

Wednesday 7 April 2010

Installing XenApp 6 – Part 4 – Web Interface

This is a 5 part guide to making a simple XenApp 6 farm.  These are the other sections:

  1. Installing a server manually
  2. Creating a XenApp 6 farm
  3. Citrix Licensing
  4. Web Interface
  5. Unattended installations

This section is about installing the web interface to support Web Interface and Agent clients.  Note Program Neighborhood will not work with XenApp 6!

  • Install a Windows 2008 R2 Server with .NET Framework 3.5 sp1
  • Launch Server Manager and add the IIS role.  Add the Windows Authentication element and the contents of Application Development.  Also add the IIS6 Management  Compatibility section further down.

image

  • Install the Microsoft Visual J# 2.0 redistributable.  This can be found on the XenApp 6 DVD at \support\JSharp20_SE\vjredist_64.msi
  • Also from the XenApp 6 DVD, run \Web Interface\WebInterface.exe
  • Choose your language, click Next and agree to the EULA.
  • You will be prompted for a folder where the clients can be copied from so they can be made available on the server.  You may not want to do this, but if you do you can use the folder Citrix Receiver and Plug-ins on the server.  These will take a while to copy as they contain lots of languages, so you might want to clear out languages you don’t want first.
  • Click next at the end of the install to start creating the sites.

image

  • You can now create XenApp Web Sites (for Web Interface users) and XenApp Services Sites (for users of the Agent). 

Creating a simple Web Interface website.

  • Specify the IIS Settings – you probably want to tick the checkbox for “Set as the default page for the IIS site”, assuming this will actually be the default page.  This will mean users will be able to just type the name of the server (or an alias you create in DNS) into their browser and see the login page of this website.

image

  • For this simple guide I’ll assume this is just an internal server that is going to host a simple website to allow Citrix access. In this case, select “At Web Interface” for the point of authorisation. 

image

  • After install, click next to configure the site.

image

  • Enter your farm name and a list of servers from the farm.  These servers should all remain up from this point on to avoid errors for users logging on.  Try to add at least two servers if you have them.  Click Next when done.

image

  • A very important choice is how users will log on to the farm.  Its unlikely you want to use Anonymous and if you don’t use Smart Cards, the third and forth options will not apply to you either.  The first two are the most usual – Explicit and Pass-through.  Explicit will prompt users for a username and password (and, optionally, a domain) before giving them their application shortcuts.  Pass-through will use the logged on Windows username and password to automatically authenticate.  This option is not applicable for every organisation as it may be considered a security problem (and obviously requires everyone to login using their own domain account on a domain PC, which might not be the case).  Pass-through is also quite complicated to get working and requires considerable testing.  When it works though, it is quite cool.  For simplicity, I’ve left it as just Explicit.  If you select more than one method you’ll need to decide later which is the default.

image

  • On the next screen you can restrict the domains allowed or allow any domain.  Probably best to tie this down to a single domain if you can for security.

image

  • Choose the layout – full or minimal.  Not a huge difference between them, especially if you are not going to put out messages on the site.

image

  • Choose whether this site will serve Online, Offline or dual-mode applications.  Online applications are normal apps when the server and client are on the network.  Offline apps are specially prepared streamed applications created with the Profiler application.  They are downloaded to the client and can be executed when the network access is not available (at least for a time).  You need a platinum farm or individually purchased license for this functionality, so if you don’t have them, choose Online.  If you do have a Platinum farm, consider whether you want to support such apps and are intending to actually create them.  Click next and finish to complete the website setup.

image

  • Open your browser and type in the name of the server, and you should see your new website

 image

  • After logon you should see any applications that you have defined for your farm for this username. 

image

  • Note you can now right click the website in the Citrix Web Interface Management tool and further configure it.  This might include adding extra Server Farms (the web interface will seamlessly merge all the shortcuts for the different farms you specify), changing authentication methods, altering timeouts, etc.

image

Creating a simple XenApp Services site.

  • Specify the IIS Settings again – this time there is no option to make it a default.

image 

  • After install, click next to configure the site.

image

  • Enter your farm name and a list of servers from the farm.  These servers should all remain up from this point on to avoid errors for users logging on.  Try to add at least two servers if you have them.  Click Next when done.

image

  • Again, choose whether to support offline (streamed applications downloaded to the client – platinum customers only) applications.  Click Next and finish.

image

  • You can now right click the website in the Citrix Web Interface Management tool and further configure it.  This might include adding extra Server Farms (the web interface will seamlessly merge all the shortcuts for the different farms you specify), changing authentication methods, altering timeouts, etc. Checking that Authentication methods is set as you would like is especially important.  Note if you want to enable Content Redirection (the ability to set local file associations on PCs to point to Citrix Applications), its here – in Server Farms > Advanced.  This is a feature of Web Services sites only, not Web Interface clients.

image

As a final step in this configuration, you might want to consider installing more than one web interface server and joining them into a NLB cluster.  This works very well with Citrix Web Interface and provides a good way of being able to make changes without removing service – i.e. you can remove a server from a cluster, update it, add it back in and then repeat with the other cluster members.

Click here: http://zenapp.blogspot.com/2010/03/web-interface-52-on-windows-server-2008.html

Tuesday 6 April 2010

Installing XenApp 6 – Part 3 – Citrix Licensing v11.6.1 build 10007

This is a 5 part guide to making a simple XenApp 6 farm.  These are the other sections:

  1. Installing a server manually
  2. Creating a XenApp 6 farm
  3. Citrix Licensing
  4. Web Interface
  5. Unattended installations

This section is about installing your licensing server and configuring your farm to use it.

  • Install another Windows 2008 Server R2 machine.  Personally I would have this be my Terminal Services licensing server as well (you WILL need an R2 server for that – a 2008 R1 server will not give you the right CALs for a XenApp 6 farm) but that’s not covered here.  Just install the Remote Desktop Services Licensing components, activate the server and add your CALs.
  • For Citrix Licensing, run this MSI from the main XenApp 6 DVD:
    \licensing\CTX_licensing.msi
    The version that ships with XenApp 6 is 11.6.1 build 10007
  • Agree to the UAC prompts and generally click Next until its installed.  There aren’t any options and it doesn’t need a reboot.
  • After installation the configuration tool will launch.  Change the licensing port if you feel the need (there’s nothing wrong with the defaults) and give it a really good password.  Don’t lose it though.

image

  • You can now launch the Licensing web interface from the Start Menu (or from another machine on the URL http://servername:8082/).  If you launch it from the server, turn off IE ESC from the server manager and try to get the localhost site into the Local Intranet security zone). 
  • In the exciting new licensing interface you should see there are now 4000 Start-up licenses – this is because Citrix don’t bother charging you by Citrix server anymore, just by concurrent user.  Therefore each installed license server can support 4000 citrix servers.

image

image

  • Click Vendor Daemon Configuration to get to the import licenses button.
  • Click Import licenses and browse to the new *.lic files.

image

  • This is the tricky part.  At this point it will probably tell you that the server name in the license file does not match the name of the license server.  If you are sure you got this right, you can probably ignore this.  Check the contents of c:\Program Files (x86)\Citrix\Licensing\MyFiles on the license server and see if the license file is there now.  If it is, restart the Windows service CitrixLicensing and then go back to the Dashboard.  You should now see your licenses.

image

  • Now you just need to enter your license server name, port and server type (Enterprise, Advanced, Platinum) in the Policies node of the XenApp Management tools (the DSC).  Its easiest to just edit the Unfiltered policy.  To start this, open the DSC, click Policies and the Computer tab.

image

  • With the Unfiltered policy selected, click Edit.
  • Select Licensing on the left and click the edit buttons by the server name and port

image

  • Then click Server Settings and “Add”, next to the XenApp product edition.  Select the edition you have licenses for and click Save.
  • Open a command prompt and run gpupdate.  If you have entered the wrong details you should get an error of “the licenses required by this edition of Citrix XenApp are not present on the license server”.  Correct the settings if you get this and run gpupdate again.  “gpupdate /force” is more effective as it will rebuild all policies rather than just looking for differences.  Reboot the server for the new Computer policies to take effect.

image

  • After the reboot, do a “query farm /load” again in CMD.  If the server still has a value of 20000 it is still not configured right.  Check that RDP is enabled in Start > right click Computer, click Remote Settings.  Check it is set to “Allow connections from computers running any version of Remote Desktop”.

image

  • If you had this problem, correct it and reboot again.  Do a “query farm /load” again in CMD and hopefully the load has gone down from 20000 (error) or 10000 (full load).  It should be more like 100.  If you still have a problem, best check your Event Viewer to see whether there is anything useful there.