Setup cannot continue version error when installing R2 on Server 2003 x64

This article is probably a few years late, but maybe you're like me and are still primarily using some version of Windows Server 2003 and haven't jumped to Server 2008 yet. I had one server running Server 2003 x64 with service pack 2 installed and decided I wanted to upgrade it to R2. I popped in CD2 of the R2 media and tried installing, but to my surprise it got an error saying "Setup cannot continue because this product disc is incompatible with the service pack installed on this computer. To complete the installation of Windows Server 2003 R2, you will need to insert the latest version of Windows Server 2003 R2 Disc 2.". At first I thought I'd be able to slipstream SP2 onto the second disk, but since the Windows install files are all on CD1 you can't do that. A quick Google search fixed my problem though, so thanks to stealthpuppy.com. Here's what to do in order to successfully install R2 on a Server 2003 x64 server running SP2.

1. Insert the R2 CD2 disk
2. Create a folder somewhere on your server and copy all the files from R2 CD2 to that folder
3. Go to your folder, then into CMPNENTS, then R2
4. Find the file named R2INTL.INF, right-click and choose Open With, then pick Notepad
5. The file should be open in Notepad at this point. Find the line that says "R2SPLevel = 1", and change that to "R2SPLevel = 2"
6. Save and close the file
7. Run R2AUTO.exe from the root of the folder you created in step #2

You should now be able to successfully install R2 on your SP2 installation. You could also burn those files to a CD or an .iso image file for future use.

How to open printmanagement.msc for managing your printers

I had never heard of print management until recently, while working on figuring out how to share 64 bit print drivers from a 32 bit server. It is a useful tool though, especially in Windows 7, so you may want to check it out. Here's how to get to it:

1. Click the Start button and type printmanagement.msc and press Enter

2. Right-click on Print Servers and select Add/Remove Server

3. Specify the server name and click OK. If you are adding your machine you can use the Add the Local Server button

OR

1. Open MMC (Microsoft Management Console) by going to Start->Run and typing mmc in the box and clicking OK. Or if you have Vista or Windows 7, click the Start button and type mmc in the Search box

2. Once the mmc window is open, go to File->Add/Remove Snap-in

3. Scroll through the list of available snap-ins until you get to Print Management. Select it and click Add

4. In the "Add servers:" box, type the name of the print server(s) you'd like to manage and click Finish

5. Click OK one more time to close the add-in manager and you should now see the Print Management snap-in

It's useful for managing shared printers on multiple print servers, and also for adding or removing drivers from your print server(s). You can also manage the local machine with this snap-in, and it's the only way I have found so far that allows you to manage the print drivers installed on your Windows 7 computer. If you're wondering how to delete a printer driver from a Windows 7 computer, the print management snap-in is the answer

Sharing 64 bit printer drivers using a 32 bit Windows print server

I've finally made the jump to 64 bit computing by adding some Windows 7 x64 machines to my environment. However, I do not have any 64 bit servers, so I wasn't sure if I was going to be able to use my existing Windows Server 2003 print server to share out 64 bit drivers for printers. Well, the answer is that you can, but without a good set of instructions it can be a little messy. Hopefully with the steps below you too can share your 64 bit drivers from a 32 bit print server.

In my situation I am working with Server 2003 SP2. If you're running R2 the steps may be different, and I'd imagine 2008 is completely different. You need your 32 bit server, and you also need your 64 bit machine. Both of them have to be used in order to load both sets of drivers. You can't load 64 bit drivers from your 32 bit server, and vice versa. The other thing is that the drivers have to be named the same. The easiest way to make sure of this is to download both the latest 32 and 64 bit drivers from the manufacturer's website and use those. That may mean you will be updating existing 32 bit drivers, but you're better off doing that than trying to get the new 64 bit driver to work with an older 32 bit driver. I currently have Sharp and HP printers printing from my Windows 7 64 bit machine through our Server 2003 32 bit server as well. In my instructions I'm going to assume you already know how to install a printer. Here's how I got it to work, and I'll use a Xerox printer for the example.

1. On your 32 bit print server, download the latest 32 bit driver for your printer
2. On your 64 bit machine, download the latest 64 bit driver

3. On the printer server go ahead and start installing the printer. Your setup may differ than what I have in the screenshots, but I'm installing a networked printer that has an IP address of 192.168.1.65

4. When asked for the print driver, click on "Have Disk...". Now navigate to the location when you downloaded your 32 bit print driver and select it. You may have to unzip the driver package you downloaded if you haven't already.

5. Pick your printer from the list included in the driver. In my case there's only one option

6. Name your printer and click Next
7. Choose to share the printer and give the share a name, then click Next
8. Fill out the location and comments boxes if you want, then click Next
9. Print a test page if you'd like, but it's not required. Then click Next
10. The printer should install and then you can click Finish
11. Now hop on your 64 bit machine and open up printmanagement.msc. If you don't know how to do that, check out my other post.
12. In the tree on the left, open up Print Servers and open your print server. Go to the Drivers section, right-click, then choose Add Driver

13. When at the Processor and Operating System selection screen, uncheck the x86 box and check the x64 box instead. Then click Next

14. Click on "Have Disk..." and browse to the location where you have the 64 bit driver that you downloaded in step #2. Again, you will have to unzip the downloaded driver file prior to being able to select it here.

15. Repeat step #5 to select your printer and click Next
16. Click Finish. This should install the 64 bit print driver on your 32 bit server

Now you can double-check to make sure it worked. As long as the printer drivers are named the same it should have. To check, log back in to your printer server. Right-click on the printer you installed and go to Properties. Go to the Sharing tab and click on Additional Drivers.

If done correctly you should see that the x64 and x86 boxes are both checked, which means the printer is being shared using both drivers.

It took some trial and error in the beginning, but this method has been working for me and I hope it works for you too. Good luck!

Free conference call service - freeconferencecall.com

If you're wondering how you're going to make your next conference call and you don't want to pay for a conferencing service, check out freeconferencecall.com. You can create a free account there and they will provide you with a 24/7 reservationless conference number you can give out to people. It's simple to do and easy to use. 

With that said, there is one thing to keep in mind. Most paid services give you a toll-free number to distribute to your callers, while freeconferencecall.com just gives you a number and some callers may have to dial (and pay) the long distance chargers involved with reaching that number. If your callers don't mind, then go ahead and save yourself a few bucks by using a freeconferencecall.com account. If you have to have a toll-free dial-in number, then you'll have to try something different. I see the same company also offers "SimpleTollFree" through simpletollfree.com , which charges you 6 cents per minute per caller. Otherwise you can always look into other toll-free conferencing options.

Windows Vista won't update, getting error 80072EFE

I had to scratch my head on this one for a while. I had someone ask me to look at their personal Vista Home Premium laptop because it wasn't able to connect to Windows Update. I had helped to remove some spyware/viruses/adware from it in the past so that was my first thought. Scans came back clean though so I went on to some other stuff. Eventually I tried installing the missing updates manually. One of those updates was the most recent Windows Malicious Software Removal tool. I figured I'd let it run a full scan and that turned out to be a good idea. It reported finding Alureon.F and removing it. However, Alureon infections can bring along a rootkit, which is exactly what happened. I removed the rootkit using TDSSKiller from Kasperky, then rebooted. My atapi.sys driver had been listed as infected. Sure enough, after everything was loaded back up the Windows updates worked fine. I ran a few more scans to make sure the rootkit hadn't been hiding anything, but they came back clean so everything is back to normal.

If you're trying to update your Windows Vista machine and getting an error 80072EFE, you may want to check for the rootkit yourself. Download and unzip TDSSKiller, then rename the executable file to something random. I used 1a2b3c4d.com (.com will work the same as .exe in this instance). Then run your executable, follow the prompts, and restart. If you want more in-depth instructions, check out this article at bleepingcomputer.com

Illustrator CS3 Unknown Error when trying to save a file

I had a user who couldn't save their Illustrator files, but had no trouble doing it the week before. It didn't matter whether she was saving locally or to the server. I tried rebooting and repairing the permissions, but neither worked. Then I trashed the Illustrator CS3 preferences and things went back to normal. If this happens to you and you don't want to lose your file, do a Save As, then pick EPS as the format. It appears that it will still let you save it as an EPS even if you can't save it as an AI file.

This was a Mac OS X 10.4.11 machine. If you're seeing this problem on a Windows install, sorry, but I don't have a fix for you. If you're not familiar with deleting preference files on a Mac, the following will explain what to do. If you have custom settings in Illustrator CS3 I'd suggest writing them down beforehand since removing the preference file will reset Illustrator to its defaults.

1. Close Illustrator CS3 if it is open
2. Go to Macintosh HD->Users->username->Library->Preferences, but substitute your actual username in where it says username
3. This is where your user account preferences are stored. Look for the com.adobe.illustrator.plist file. Move it to your Trash, but you don't need to empty it
4. Now, within your Preferences folder, find the "Adobe Illustrator CS3 Settings" folder and move that to the Trash, but do not empty it
5. Start Illustrator CS3. This should create new preferences files containing the default settings for Illustrator CS3.
6. Open or create a document, then try to save


If you get to step 6 and it works, then you're set. If you had customized settings in Illustrator you will need to set those up again since removing the preferences also removes any customizations to the settings. If you had them but do not remember what they were, you can get your preference files from the Trash, restore them to where you found them, then open Illustrator again. That way you can see what your customizations were, remove the preferences again, then set up the preferences while working with a good set of preference files that allow you to save.

If you still can't save after step #6, you have the option to put the preference files (com.adobe.illustrator.plist and Adobe Illustrator CS3 Settings) back into your Preferences folder and restart Illustrator. That way your settings will be back and you can go on troubleshooting your problem saving without losing any customizations to the application.

How to install CUPS-PDF in OS X 10.6 Snow Leopard

Adobe did away with it's Adobe PDF printer in OS X 10.6 stating enhanced security prevented it from working. However, CUPS-PDF does the same thing and is free to download. Update 12/7/10: From the comment below from Jeff Z, it sounds like the CUPS-PDF install package has been updated to work with Snow Leopard without all the Terminal tweaks below. You should be able to download, install, and use without having to perform any of the tweaks below. I've left them in the article though for completeness.

If you're installing CUPS-PDF on Snow Leopard, there are some things you need to do in order to get it working though.

1. Download and install CUPS-PDF. You can get it from here in the Downloads section. It says there is an updated version for Snow Leopard, but that still doesn't help you avoid the rest of this.
2. Once you have CUPS-PDF installed, open a Terminal window. You can find that by going to Macintosh HD->Applications->Utilities->Terminal
3. In Terminal, use the command sudo chmod 0700 /usr/libexec/cups/backend/cups-pdf to change the permissions on the CUPS-PDF install
4. Now, change the ownership using sudo chown root:wheel /usr/libexec/cups/backend/cups-pdf
5. It gets a little tricky here because you have to change a configuration file. It's not hard, but most people probably haven't had to do it before. Use the command sudo vi /etc/cups/cups-pdf.conf to open the file in the VI text editor
6. In the file, scroll down to where it says "Out ${HOME}/Desktop/cups-pdf"
7. Press 'a' on the keyboard, which will put VI into edit mode. Now change the line in step #6 to instead read "Out /var/spool/cups-pdf/${USER}", but you don't need the quotes
8. Now press ESC on the keyboard, then type ":wq" (without the quotes) and press Enter. This will write your changes to the files, and also quit the VI editor
9. Now use the command sudo ln -s /var/spool/cups-pdf/${USER} ~Documents/CUPS-PDF to put a shortcut to the CUPS-PDF save location in your Documents folder
10. You can close the Terminal at this point and shouldn't need it again. Open System Preferences
11. Go to Print & Fax
12. Click the + to add a printer
13. Under the Default area, you should see CUPS-PDF in the list of available printers. Select it and choose Add.

Now you can use the newly installed CUPS-PDF printer to create PDF files, and don't need to use Adobe's workaround of "Save as PDF". To get at your printed PDF files, go to Documents folder and follow the CUPS-PDF shortcut. You can move that shortcut to your Desktop if you'd prefer to have easier access to the shortcut location of where the files get created. One downside of this is I believe you have to go through this process for each individual user on a machine that will need to use CUPS-PDF. You can skip a few of the steps, but the rest could turn into a pain if you have a lot of users on each machine.

Thanks to the macosxhints.com forum for helping sort this one out.

Error c1041739 when mounting a mailbox store in Exchange 2003

I ran into error c1041739 "The database files in this store are inconsistent" when trying to mount a restored mailbox store on a backup Exchange 2003 server. It wasn't too hard to fix using some of the Exchange command-line utilities though. You may want to make a copy of your .edb and .stm files prior to performing any activities on them, just to be safe. For this example, let's say I have priv1.edb and priv1.stm both in the C:\Mail folder and am getting error c1071739 when trying to mount priv1.edb. Here's how I would attempt to fix it:

1. First, open a command prompt
2. Change to the C:\Program Files\Exchsrvr\bin folder using cd "C:\Program Files\Exchsrvr\bin". This will put you in the location of the Exchange command-line utilities. If your program files folder is somewhere else, change the path in the command accordingly
3. Now, use eseutil /p on the .edb file. In my example, this command would look like eseutil /p "C:\Mail\priv1.edb"
4. Once that finishes, defrag and rebuild the edb database. To do that, use eseutil /d /t:C:\tempEmail "C:\Mail\priv1.edb". The /t:C:\tempEmail is telling the command to use C:\tempEmail as the temporary location for the defrag files. You can change that location to wherever you want, so feel free to use a different folder or a separate partition that fits your needs. The defrag can take some time if you have a rather large .edb file.
5. Once the defrag is complete, use eseutil /mh "C:\Mail\priv1.edb" to check the consistency of your file. You should not get any errors at this point.

That's all I had to do. Mounting the mailbox store after the repair worked fine, and I was able to retrieve the information I needed. There are a few steps I left out, but if this doesn't work for you check out Microsoft KB 906148. It covers the c1041739 "The database files in this store are inconsistent" error, along with the steps Microsoft recommends using to fix it. Good luck!

Black box around things or computer is talking to you in Mac OS X

If you're using a Mac and all of a sudden your Mac starts speaking to you, or you start seeing a black box outlining everything you click, it's ok. Your computer is not possessed. Instead, you probably enabled the VoiceOver feature. You can do this by pressing Command+F5 (which toggles it on and off), or through the System Preferences. To shut it off either use the shortcut keys, or go to System Preferences->Universal Access and turn VoiceOver off. That will get rid of the black box outline, and also stop your computer from talking.

Of course, if VoiceOver is not turned on and your computer is still talking to you, then it may be possessed and you'll have to find a computer exorcist... You only need to watch from 0:20-1:00 to see what a computer exorcism is all about.

How to disable Windows 7 Aero snap feature

You may have seen the new window snap feature advertised in the commercials for Windows 7, but after using Window 7 for a week I can tell you that it is really annoying. Luckily you can turn it off with one check box. If you're like me and can't stand it, here's how to shut it off.

1. Go to Start->Control Panel->Ease of Access
2. Open the Ease of Access Center
3. Find the "Make the mouse easier to use" link and click it
4. Scroll down and check the box that says "Prevent windows from being automatically arranged when moved to the edge of the screen" and click OK

Now you can move your windows around again without having them snap to positions or automatically resize themselves. If you have trouble following those instructions, try the howtogeek.com walkthrough that has screenshots.