SBS 2008 – Multiple Lacerte 200X Install Initialization Procedure on One Workstation – Including 2003

We have posted about our experiences with installing previous versions of Lacerte on an SBS 2008 domain with 100% Windows Vista workstations:

• SBS 2008 - Migrating Lacerte 2006 onto Windows Vista

• SBS 2008 – Lacerte 2005 Install

• SBS 2008 – Lacerte 2004 Install

We now have Lacerte 2003 and up installed on all of the Windows Vista workstations with the databases stored on a network share. The procedure was the same as the 2004 version.

What we did to install all versions on the same system:

1. Install Lacerte 2006, 2005, 2004, 2003 in that order.
2. Only reboot after the Lacerte 2003 install completes using the 2006 reboot dialogue (leave dialogue open).
3. Answer NO to the reboot question in the 2005 version install and down.

Once the workstation has rebooted after the 2003 install, each version of the program needs to be initialized.

We found that if we ran through firing up each of the programs, one at a time, from 2006 on down, we ran into problems with the 2004 and 2003 versions hanging on a double click of their shortcuts.

When we reversed the order, that is starting the initialization process with the 2003 version, then the 2004 version and so on, we were able to initialize each program in order without any problems with a program hang.

Keep in mind that each program needs to be opened individually and not simultaneously during the initialization steps. Also, the 2004 and 2003 versions can take a lot longer to start up for the first time relative to the newer versions.

So, keep a Workstation Install check list handy for each installed version as well as each version that has been initialized when installing to more than a couple of workstations.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts will not be written on a Mac until we replace our now missing iMac!

Windows Live Writer

SBS 2008 – Lacerte 2004 Install

We had some interesting times getting Lacerte 2006 installed and configured on an SBS 2008 network (Previous blog post).

And, today we also installed Lacerte 2005 (Previous blog post) into an SBS 2008 and Windows Vista Business native environment.

Have a look at both posts in order to get the run down for each version of the program.

In the case of Lacerte 2004, once the network install was completed (again from a local folder to UNC path), we needed to copy the network installed 04Tax folder to the local machine and run the workstation specific install from there.

We left the workstation install directory at the default C:\Lacerte\0XTax for all of our installs so far.

Once the install routine had finished, the program fired up okay with a series of typical Lacerte startup questions.

This one was pretty neat:

We have not seen a 15” monitor sitting on a desk for a long time. In this case, the question is probably referring to a CRT monitor size too. Perhaps the only exception to that rule would be the occasional 15” LCD sitting on a table in a server closet or in an older 1U KVM drawer.

Again, keep in mind that Lacerte 2004 will need to be fired up at least once before copying over the existing Lacerte 2004 firm data on the first install to the network and local workstation.

On each subsequent workstation Lacerte 2004 gets installed on the program will take some time to fire up, so please be patient.

To date, we now have the following successful Lacerte network installs with full firm data access on an SBS 2008 and Windows Vista Business native network:

Lacerte 2008, 2007, 2006, 2005, and 2004 on SBS 2008 & Vista

We have one more install to do for Lacerte 2003. Hopefully it will go as good as the previous versions did … at least relatively that is! ;)

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts will not be written on a Mac until we replace our now missing iMac!

SBS 2008 – Lacerte 2005 Install

We had some interesting times getting Lacerte 2006 installed and configured on an SBS 2008 network (Previous blog post).

We just finished running through various combinations of set up attempts to get Lacerte 2005 installed to a network location.

Essentially, we discovered that the setup and data migration ran the same as it did in the previous post for Lacerte 2006 with one exception.

It turned out that no matter how we tried to get the install to run from a network location, it would not. Lacerte 2005 would not recognize the mapped drive we were running the install from. It always assumed we were running from a UNC path \\server\Lacerte\setup.exe.

Once we copied the install CD contents to a folder in a local folder, we were able to run the install to both the network mapped drive and to the local machine without a problem. Make sure not to use a folder that is redirected to the server such as the Documents or Desktop folders as setup will fail.

Again, keep in mind that Lacerte 2005 will need to be fired up at least once before copying over the existing Lacerte 2005 firm data.

UPDATE: Some of the workstations are complaining about installing from a UNC instead of a mapped network drive. If that happens, copy the 05Tax folder over to a local folder and run the setup from there.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts will not be written on a Mac until we replace our now missing iMac!

SBS 2008 - Migrating Lacerte 2006 onto Windows Vista

We just finished a successful integration of the Lacerte 2006 software on an SBS 2008 domain with 100% Windows Vista workstations.

Lacerte 2006 on Windows Vista

What we discovered was this:

• The install files must lie on a UNC such as:
  • file://ss-sbs/Company/Lacerte/06Lacerte/Setup.app (.exe)
  • No spaces allowed in any of the folder names!
  • Keep the file location simple as above.
• The Setup.exe file needs to be run from a workstation.
• The first network install goes to:
  • \\ss-sbs\Company\ProgramData\Lacerte\06Tax
  • Again, note the lack of spaces in the folder names.
  • Windows Vista uses a folder called ProgramData so we copied the name for all server installed applications.
  • Lacerte will warn about running it on Windows Vista as shown above, click the Continue button.
• Once the install finishes, the workstation install will need to run.
  • Leave the default C:\Lacerte\06Tax folder to install to.
  • Allow it to run the updates notifier.
  • Allow it to install the MSDE that it needs locally.
  • The Vista Warning will pop up again, this time check the Don't show this again option.
  • A reboot of the workstation will be required.
• Run the program. If it warns you again, make sure to check the Don't show this again option and it should no longer bother you.
  • It may stall a few times on various set up routines. Just be patient. The program will begin to respond.
  • Note that the firm's Federal ID Number will be required once the program fires up.
• Once the first workstation install has fired up, a new IDATA folder will show up in the 06Tax folder. Close the program and do the following:
  1. Rename the new IDATA folder to IDATA-Original.
  2. Copy the firms existing data folders into the 06Tax folder.
  3. Restart Lacerte 2006 and the firm's data should be there.
  4. NOTE: Do not copy the firm's data into the 06Tax folder until such time as Lacerte 2006 has had a successful start up after the first workstation install.

This is what the 06Tax folder looked like after we had transferred the firm's existing data into the folder and had a successful connection via one of the workstations:

The Firm's existing Lacerte 2006 data folders are good to go

Once everything is in place, we installed the rest of the workstations following the above steps (without the need to do a network install) via the installed application's UNC path:

• \\ss-sbs\Company\ProgramData\Lacerte\06Tax\Setup.app (.exe)

While we have not run through our testing of the Lacerte 2005 program, if it shares the same code base as Lacerte 2006 then it should install and run okay.

One thing to keep in mind in this particular case is that we already have a number of applications installed on the Windows Vista workstations that utilize similar components to Lacerte.

So, we did not encounter any problems with the Windows Firewall with Advanced Security. If a connection cannot be completed, make sure to Unblock any service request warnings by the firewall. Enable the logs on the server and workstation to check for dropped packets and any rules that may need to be created. Port 1433 probably would show up due to the SQL MSDE instance on the workstations.

One caveat to warn users about:

Lacerte 2006 - Error on Shutdown

They may experience an application hang when shutting down the program. They need only wait until the Cancel button changes to Close program and click on that. This is, unfortunately, one catch for running older applications on a newer OS.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

 Subscribe in a reader

SBS 2008 - Enable UAC by default in Group Policy

We ran into a strange struggle while troubleshooting a client's line of business application today.

SBS 2008 is the primary server with all client computers running Windows Vista Business Service Pack 1.

We have set up a limited domain user account that was pushed out to all of the client computers and subsequently added to the local admin group on them for software installs and system configuration changes. The password on this account has not been rotated yet as this is a relatively fresh install. It will be rotated on a regular basis once things have settled in.

Remote Assistance in SBS 2008 allows the user to check a box to transfer UAC prompts to the one providing the remote assistance. But, they first need to affirm that setting by receiving a UAC prompt.

When we were providing remote assistance for the LoB and the user enabled the setting to transfer UAC prompts to us, no UAC happened. We knew this because the RA window goes black during that initial UAC prompt.

It did not take long to see that the user had managed to disable the Windows Vista UAC prompt altogether.

Well, we do not want that to happen. So, to eliminate that happening again, we are going to enable UAC by default using Group Policy:

Enable UAC by default in Group Policy

We created and linked a GPO called Default Computers Policy to the Computers OU, disabled User settings, and set the following under Computer Configuration --> Policies --> Windows Settings --> Security Settings --> Local Policies --> Security Options:

• UAC: Behavior of the elevation prompt for administrators in Admin Approval Mode: Prompt for credentials
• UAC: Behavior of the elevation prompt for standard users: Prompt for credentials
• UAC: Detect application installations and prompt for elevation: Enabled
• UAC: Run all administrators in Admin Approval Mode: Enabled

Note that we set a comment into the properties of the GPO itself to keep track of the GPO's creation date, the changes we made and when they were made. We do this for all GPOs, but in this particular case the Windows Settings node does not allow for comments on each setting, so it is particularly important to make note of any changes we have made.

The Administrative Templates nodes for both User Configuration and Computer Configuration allow for us to comment on the individual settings. We also comment when we have made changes to any settings in those nodes too.

Once the new settings have been updated on the client workstations, the UAC will not be able to be disabled.

UAC is, in our experience, one of the best ways that a user can use to prevent any malware or virus infections. Once a user is aware of the implications when they see a UAC prompt, and they know they need to cancel, unless they initiated a software install, it is virtually impossible for any bad software to take hold of the system.

We did the opposite of Petri's Method #3 to disable UAC in Group Policy: How can I disable the User Account Control (UAC) feature on my Windows Vista computer?

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

Java Setup Errors 2755 and 1624 on Windows Vista

We had a really strange fight to get the Jave runtime to install on a client's Vista Business SP1 laptop.

No matter what we tried while logged in as the user we would always get:

Java Setup: Internal Error 2755. 1624, ...

Note that the install .msi file is not in a temp folder but under its own subfolder.

Just in case we emptied out the Temp folders both under the user's profile and under the %windir% to no avail.

We went to the Java Manual Download page and downloaded the full Offline version for Windows.

Still we did not get anywhere.

A bit of searching turned up the following in Sun's Java forums: Java Install / Autoupdate - Help Please:J2RE Installation fails - "Internal Error 2755. 1624, ".

We followed each suggestion as we progressed down the various posts. None of them worked until the post by JimDenver on 09/18/07 to start the .msi install from the folder listed in the error.

We did that and we were eventually greeted with:

Java Setup - Progress: Installing Java

The install kept going until it hit the "Registering Components" phase. Then it just sat there.

We left it alone for about 5 minutes which was an abnormally long time for an install on a laptop as powerful as the one we were working with.

One of the notes in the forum posts talks about antivirus or antispyware blocking the install. So, we brought up the Task Manager and sure enough for every CPU cycle the Windows Installer was taking up Windows Defender was taking up twice as much. It looked as though there was a competition going on between the two.

We killed the Windows Defender process and within seconds the Java install showed:

Java Setup - Complete

Just to make sure the Windows Defender blockage did not cause any further issues, we went to the Verify Java Version page and ran the test. We were given a successful install of Java 1.6.6 page!

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

SBS - Windows Vista - Simply 2008 Install Quirck

It may seem that Sage has taken a step backwards in their Simply Accounting setup for version 2008.

Simply 2007 installed with no issues on Windows Vista with the data hosted on a network share.

Simply 2008 on the other hand does not install as simply as that.

The first problem was on the Windows Vista workstation.

Whenever we went to run Simply Accounting we would get:

Error: Cannot connect to Simply Connection Manager

On a properly running setup we should see:

Simply Accounting Connection Manager Service

The little icon was in the System Tray, the service was installed and listed under services.msc, but it was not running.

This is what we had to do:

1. Open Windows Explorer (logged in as a local admin) or elevate Windows Explorer
2. c:\Program Files\Winsim\ConnectionManager
3. Right click on the SimplyConnectionManager.exe file & properties
4. Compatibility Tab
5. Run this program as an administrator
6. Apply
7. OK
8. Close Windows Explorer.

This is what we would see during the above process:

Setting Admin Rights to the Connection Manager

Once we did that, we hit the start button for the service and it started with no issues.

But, we encountered the same error again!

This client's data is located on a company share, so we were not sure what the next step was.

Since this is a brand new install, we put in a call to Sage to see what they had to say.

Well, apparently we need to do a "Data Only" install on the server. Once we did that, made sure the Simply Connection Manager service was started - it did not start up after the install - they were in business.

There are two workstations connecting to this database. One of the two needs to be running as a restricted user.

And we may be in a bit of a bind as the service is not wanting to start while logged in as the restricted user. We even set the service to run as admin via an elevated Windows Explorer and subsequent UAC elevation using a local admin rights user to access the "Run as Admin for All Users" properties.

It is the end of the day for them, and for us, so we will work on it again in the morning to see if we need to set compatibility mode for the service in order to get it to run under a restricted account. But, so far we have struck out.

Sage ... it is not looking too good for you at this point. :(

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

System Builder Tip: Vista Business OEM Downgrade Rights

Folks, if you are like me and you have clients not ready to run Vista Business or Ultimate on their SBS networks, get yourself an XP Pro SP2 Fully Packaged Product ASAP! You can use that media to install and validate the downgrade XP Pro SP2 Retail for your client.

The OEM method, as explained further down, could be a bit of a struggle as you would need to make sure that you have their old system with the XP Pro SP2 COA on it! So, make sure to advise them to bring in the old system before tossing it into recycling or passing it on.

Microsoft Licensing today indicated to us that we could use the retail key to install and validate the downgrade version as many times as is required. Product Activation need only know that we are authorized system builders installing a downgraded OS.

A reason for indicating that one needs to grab an XP Pro FPP is because they are becoming few and far between at the Big 3 or 4 distributors here in Canada. I am sure that the U.S. may be the same. The Microsoft Licensing Rep mentioned that the Retail key can be activated with no issues, or the System Builder can call the Activation Centre to get it activated with little or no issue. Your Microsoft Partner ID or System Builder ID may be required for this service.

From Microsoft's document: Microsoft Select License, Open License, Original Equipment Manufacturer (OEM) License, and Full-Packaged Product (FPP) License Downgrade Rights

Can I downgrade my OEM version of Windows Vista Business to Windows XP Professional?
Yes. OEM downgrade rights for desktop PC operating systems apply to Windows Vista Business and Windows Vista Ultimate as stated in the License Terms. Please note, OEM downgrade versions of Windows Vista Business and Windows Vista Ultimate are limited to Windows XP Professional (including Windows XP Tablet PC Edition and Windows XP x64 Edition). End users can use the following media for their downgrade: Volume Licensing media (provided the end user has a Volume Licensing agreement), retail (FPP), or system builder hologram CD (provided the software is acquired in accordance with the Microsoft OEM System Builder License). Use of the downgraded operating system is governed by the Windows Vista Business License Terms, and the end user cannot use both the downgrade operating system and Windows Vista Business. There are no downgrade rights granted for Windows Vista Home Basic or Windows Vista Home Premium.

A document download called, "Windows Vista Downgrade Rights" that I can't seem to locate the actual Microsoft download page for, can be found here (PDF). This document gives a visual presentation of Windows Vista Downgrade Rights along with a straight forward FAQ.

It also explains that in the case of downgrading Windows Vista Business OEM the CLIENT is to provide the OEM key!

For larger System Builders who have a spool of COAs with their OEM packs, this may not be much of an issue as of yet. But, for the smaller System Builders and OEMs it may become one very quickly as the Big 3 or 4 here in Canada have NO stock on XP OEM product. I suspect that this is also the case in the U.S. and other places.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

Virtual Vista - Blue Screen STOP 0x000000D1

DRIVER_IRQL_NOT_LESS_OR_EQUAL

I was doing some tweaking on our two virtual Vista Business installations. They were both rebooted at the same time, with one BSOD as above.

The system is a new SR2300 with dual 2.8 GHz. Xeons and 6 GB of RAM. Drives are a pair of Seagate SCSIs mirrored by the host OS.

The funny thing is, the other instance just kept trucking. A "reboot" of the virtual machine allowed the instance to boot with no issues.

There is no virtualization tech on this particular machine. So, there could be any number of reasons why it happened. One is an attempt to hit a spot in memory that was already occupied, another being something with the hardware itself.

Some further testing will be in order. Though, in this case the Vista machines are for testing purposes only. We also have two XP Pro SP2 instances on it that are running quite stable. So, time will tell as we tear Vista apart, and put it back together again!

I like that ability with the virtualized OS: Kill it, then kill it again, then kill it again...As long as my original VHD copy is around, I am good to go!

The machines are virtualized on Microsoft's Virtual Server 2005 R2 Enterprise Edition.

Microsoft's take on it: KB 293077 Error Message: STOP 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL.

UPDATE 2009-04-01: The above link is now a dud. Here is a link for a search for the stop error on Microsoft's support site: 0x000000D1 Search.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

Office 2007 and IE 7 peformance on XP Pro Versus Vista Business

Is it just me, or does Office 2007 and IE 7 run like dogs on XP Pro SP2?

The reason I ask this is because the XP Pro SP2 based system I run in the Office is no slouch!

• Intel QX6700 Quad Core Extreme


• Intel 975XBX


• ATI X1900 CrossFire & X1900XTX Video


• 4 GB Kingston RAM

It may be possible that I am experiencing some sort of configuration issue, but nothing comes up in the diagnostics for Office that I can see.

The system at Home running Office 2007 and Vista Business is configured as follows:

• Intel P4 650 3.4 GHz. HT


• Intel D925XCEV2


• ATI X850 PCI-E


• 4 GB Kingston RAM

Office runs so smooth, as does IE 7.

When it comes to IE 7, we are running a smaller Internet connection at home, 1.5 Mb/s as opposed to the 4.0 Mb/s here in the office where the XP box is. Makes for even more puzzlement.

Same sites on both machines, XP & IE 7 renders slower than Vista and IE 7.

I can remember hearing at the various Microsoft events that I attended that Vista, Office 2007, and IE 7 were meant for each other.

This experience of mine working with both OS configurations on fairly high end machines definitely puts some truth to that!

By the way, both the home and the office are Small Business Server 2003 Premium integrated with Exchange 2003 SP2.

The big thing for me at this point is to wait until the more exotic components that I have plugged into the system here in the office has Vista drivers that are no longer in Beta. I will then blow away the box and build on Vista Ultimate as we are licensed for it via our Software Assurance.

In my experience, Vista, Office 2007, and IE 7 rock together!

Happy Vista, Office 2007, and IE 7 Operating!

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

Virtual Vista Windows Experience Index

We are testing out Vista in a virtualized environment. The following is the message one will receive if the Assessment is run when connected by TS into the virtual machine:

It won't run. Period.

Vista Business RTM (TechNet) is the version of the operating system installed.

Here is the message one will receive when connected via the Virtual Server Web Console:

There isn't a whole lot out there about this, but I suspect that it has to do with the fact that Vista is running on virtualized hardware.

Not a big deal, just an interesting quirk.

Happy Vista Virtualizing!

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists