Xen App server - MMC failed to create empty document

When trying to launch any application that uses MMC, an error appeared Microsoft Management Console - failed to create empty document.

Solution:

I checked the knowledgebase article on Microsoft website that talks about checking for the Temp folder location and disk space on the hard-drive. My setttings appeared to be fine, the Temp location was at c:\documents and settings\%username%\local settings\temp

It seemed that the profile for the user logging in was corrupt, I was able to resolve the issue by deleting the user's roaming profile.

Can not reach company website from internal network

Our internal and external domain are the same, for this discussion let's assume that domain is "somedomain.com". We switched webhost and we started to have issues with not being able to reach our company website "www.somedomain.com" from the internal network. If your internal and external domains are the same, then your internal computers will look for "www.somedomain.com" to be inside your network, even if your DNS forwarders are working fine. If you are having same issue then you have to know that there are couple of things you have to do in your internal DNS so that your internal computers can resolve your website, www.somedomain.com.

In your Internal Network on your DNS server create a new Forward Lookup Zone. Go through the new Zone creation wizard. When asked for name, name this Zone www
After the zone is created, created a Host (A) Record in this forward lookup zone that points to the IP address of the host that is hosting your website. You can leave the name blank, your host record would look something like this.

Eg.

same as parent folder Host (A) 67.45.45.45 (this is the IP address of the external host)



Please note, that if you know the FQDN (fully qualified domain name) of the host that is hosting your external website then you don't have to create the new zone, you can just create an Alias (Cname) record in the Forward lookup zone of your domain pointing to the FQDN of that host.

Eg.

www CNAME virtual.sitehost.com

SSL Certificate Expiration error on Web Interface Server after renewing

Yesterday I renewed our SSL Certificate on Citrix Web Interface Server. I went through the drill of creating the CSR and then sending it to Entrust. After renewing the certificate in IIS, the user's were still getting the error that the Certificate was expired.

We have Citrix Secure Gateway installed on the WI server, turns out after you renew the certificate in the IIS, you have to run the CSG configuration wizard to replace the current certificate. When you run the CSG wizard there will be a step where you will be shown your old certificate and your new one, you just pick the new one and complete the wizard and that should take care of the above issue.

Renewing Certificate on Web Interface Site with CSG

I am running Citrix Secure Gateway on my Web Interface Server. When my SSL certificate expired on the site I renewed with the CA. After I installed the new certificate on IIS, I started having couple of issues.
First, the default site would not start. It was in a Stopped state and when i tried to start it, I receved the error:

" The process cannot access the file because it is being used"

This was because the default site had it's SSL port set to 443, and if you have CSG installed, by default it will use Port 443 for SSL, so change the SSL port in the Default site to 444. This resolved the issue for me and the default started with no error message.

Quickbooks and Terminal Server 2003

If you call Intuit tech support and ask them about Quickbooks on Terminal server the answer most likely you will get is that "Quickbooks is not supported on Terminal Server" . Only Quickbooks Enterprise is supported on Terminal Server.

However, I was not going to NO for an answer so I started doing some research and found that there are tweaks that one can use to make Quickbooks to run in a Terminal Server environment.

Users must be given some special priveleges for this to work, here are the steps that I used that worked for me.

• perform a normal installation of QuickBooks (in install mode!)
• reboot
• enter install mode again (change user /install), start QuickBooks and activate it by entering the registration code (this is a crucial step, and must be performed immediately following the reboot
• go back to execute mode (change user /execute)
• copy the %systemroot%\Intuit folder into each users %userprofile%\Windows folder
• create a Quickbooks Users group
• add your users to this group
• give the group Full Control to HKEY_LOCAL_MACHINE\Software\Intuit\QuickBooksRegistration
• give the group Full Control to HKEY_CLASSES_ROOT\.QPG
• give the group Full Control to HKEY_CLASSES_ROOT\obja.obja
• give the group Full Control to HKEY_CLASSES_ROOT\Quickbooks.application - QB Premier 2004 only?
• give the group Modify rights to the %Program Files%\Intuit folder
• give the group Modify rights to the %Program Files%\Common Files\Intuit folder

Printing Issues:

Printing is always a challenge in Terminal Server Environment and with Quickbooks there are couple additional caveats.

If your printer is working in all other applications except for Quickbooks chances are that the printer has a long printer name. Quickbooks does not support printer names longer than 64 characters,
So you must shorten the name of the printer on your end and then reconnect to the terminal server.

Adobe 8.0 Installation Error 1406

Yesterday I ran into an issue with installing Adobe 8.0 on a user's computer which was running Windows XP SP2. The installation error was 1406, access is denied. It pointed to certain keys in the registry which the installation program could not write to.

After checking the permissions on the registry keys that the error pointed to, I found out that the I was not set as the owner on these keys.

After changing the permissions on the registry keys (changing ownership), the program installation continued without a hitch.

Please note that to get the details on how to change the registry key permissions please refer to the Adobe forum that talks about the error 1406.

Restoring deleted emails from Outlook 2007

Recover deleted emails in Outlook 2007

Have you ever accidentally deleted an email that you needed and you didn’t know how to get it back? If you are using Microsoft Outlook 2007, there is a possibility that you can get that email back. Microsoft has a very easy way to see the emails that it can recover from the depths of your email.

Make sure you have Outlook 2007 open. On the main menu click “Tools” and click the “Recover Deleted Items” option.

The Recovery window will open and display all emails that can be recovered. Click on the email(s) that you want to recover and click the “Recover Selected Items” button (it’s the second button in the top menu).

All emails that you have selected will be put back in the original folder that you deleted them from. So if you deleted the item straight from your Inbox, the email will be put back in your Inbox.