Showing posts with label Office 2007. Show all posts
Showing posts with label Office 2007. Show all posts

Tuesday, 11 May 2010

Further to Licensing Office in a Terminal Services Environment

Eric Ligman kindly wrote a follow-up e-mail asking about the scenario posted in our earlier post today on Licensing Microsoft Office in Terminal Services.

And the clarification made by Eric:

  • Office is licensed per _device_ accessing the application no matter where the application is installed.

In the original post we had _desktop_

So, in the previously mentioned situation where we have 22 users total with 11 of them locally and 11 of them remote, we need to keep count of the number of _devices_ being used to access Office on the Terminal Server.

For example:

  1. 22 users using Office.
    1. 11 Office users on 11 local PCs (11 devices).
    2. 11 users on 11 remote PCs into Terminal Services Office (11 devices).
    3. Licenses required: 22.
      • This is our original situation.
  2. 22 users using Office in a shift work environment.
    1. 22 Office users on 11 local PCs (11 devices) via 2 shifts
    2. Licenses required: 11.
  3. 22 users using Office on multiple PCs and laptops.
    1. 11 Office users on 11 local PCs (11 devices).
    2. 9 users on 9 remote PCs into Terminal Services (9 devices).
    3. 2 users on 2 remote laptops into Terminal Services (2 devices).
    4. Same 2 users on 2 remote PCs into Terminal Services (2 devices).
    5. Licenses required: 24.
  4. 22 users using Office on multiple PCs and laptops.
    1. 11 Office users on 11 local PCs (11 devices).
    2. 7 users on 7 remote PCs into Terminal Services (7 devices).
    3. 4 users on 4 remote PCs into Terminal Services (4 devices).
    4. Same 4 users on 4 remote laptops into Terminal Services (4 devices).
    5. Licenses required: 26.

Thanks Eric for making sure that we were absolutely clear on how Office licensing works.

With that clarification we can be 100% confident that we will offer the correct answer to our clients when they ask about delivering Office to remote users via Terminal Services!

Eric’s original post:

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Licensing Microsoft Office in Terminal Services

This post has an update here: Further to Licensing Office in a Terminal Services Environment.

This one is a bit of a brain buster to figure out, though Eric Ligman has done a great job of clarifying the way to properly license Microsoft Office in a Terminal Services environment:

Essentially:

  1. Office is licensed per _desktop_ _device_ accessing the application no matter where the application is installed.
  2. Open Licensing provides the rights to run Office in a Terminal Services environment.

So, we have a client that we are setting up that has a combined total 22 users in their Active Directory with 11 physical machines on the network and 11 users connecting remotely via TS Gateway on SBS to their internal Windows Server 2008 R2 Standard Terminal Server.

Office and their Line of Business application will be delivered via TS RemoteApps as well as Remote Desktop Services for certain users that require a desktop to work from.

All 11 systems will have Office and all 11 TS users will be accessing Office on the Terminal Server so we will be providing them with a sum total of 22 Open Value based licenses.

A couple of key Office Open Value part numbers:

  • Office 2007/2010 Open Value 3 Year Agreement with 3 Payments
    • 021-07257: Office 2007/2010 Standard
    • 269-09046: Office 2007/2010 Professional Plus

The Microsoft License Advisor site:

There are three physical servers on this particular network with SBS 2008 Premium and Windows Server 2008 R2 being licensed with an Open Value Agreement.

UPDATE: Eric kindly e-mailed us with some clarifications based on our client situation mentioned in this post. His thoughts are developed with some examples in our post Further to Licensing Office in a Terminal Services Environment.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Tuesday, 24 November 2009

Office 2010 Beta – Office 2007 Uninstall Fail?

After uninstalling Office 2007, we installed Office 2010 Beta. But, things were not working as we had expected. So, into the Programs and Features we went on this Windows 7 laptop and we found:

image

Note that the above was found after uninstalling Office 2007 and rebooting the laptop.

So, what does that mean?

It means that the script used to deploy Office 2007 on our network via Group Policy does not detect the newer version installed on this laptop and proceeds to install Office 2007.

It looks as though the script is not aware of the 64bit versions. We will need to look into updating it to work with the new versions of Office 2010 when we have access to our Open Value Licensing version.

The script:

setlocal

REM *********************************************************************
REM Environment customization begins here. Modify variables below.
REM Modified 2009-10-06 by Philip Elder for company variables.
REM *********************************************************************

REM Get ProductName from the Office product's core Setup.xml file.
set ProductName=Enterprise

REM Set DeployServer to a network-accessible location containing the Office source files.
set DeployServer=\\SBS\ClientApps\Office2007Ent

REM Set ConfigFile to the configuration file to be used for deployment REM (required)
set ConfigFile=\\SBS\ClientApps\Office2007Ent\Enterprise.WW\config.xml

REM Set LogLocation to a central directory to collect log files.
set LogLocation=\\SBS\ClientApps\Office2007Ent\Office12Logs

REM *********************************************************************
REM Deployment code begins here. Do not modify anything below this line.
REM *********************************************************************

IF NOT "%ProgramFiles(x86)%"=="" SET WOW6432NODE=WOW6432NODE\

reg query HKEY_LOCAL_MACHINE\SOFTWARE\%WOW6432NODE%Microsoft\Windows\CurrentVersion\Uninstall\%ProductName%
if %errorlevel%==1 (goto DeployOffice) else (goto End)

REM If 1 returned, the product was not found. Run setup here.
:DeployOffice
start /wait %DeployServer%\setup.exe /config %ConfigFile%
echo %date% %time% Setup ended with error code %errorlevel%. >> %LogLocation%\%computername%.txt

REM If 0 or other was returned, the product was found or another error occurred. Do nothing.
:End

Endlocal

So for now, we will restructure our OU and GPOs for the moment to exclude the GPO setting to deploy Office 2007 for any machines the Office 2010 Beta will be installed on.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Wednesday, 14 October 2009

“We need 3 PCs Networked Please.”

While in Las Vegas a lady left a voicemail asking us to help them out with networking together 3 PCs.

A quick call back to them late last week to let them know we received the message but were getting caught up and would get back to them led to another call last Friday and a chat with the general manager (GM).

They had spec’d out a Dell server at $8,000 for their needs!

Okay, so we needed to see what was going on so we arranged for an appointment that ended up happening this morning.

To date, none, none of the other I.T. service providers had called them back besides us.

Think about that for a second.

No one bothered to call back to even ask them what it was they were looking for. No one thought about how 3 users connected to Exchange and SharePoint hosting (OWN) resold by them would add that little bit more to the bottom line.

The icing on the cake was the actual visit.

It seems that the lady that put out the feeler call to all those I.T. shops including our own had somehow managed to interpret the GM’s instructions about getting things networked together to mean her machine, the QuickBooks user’s machine, and the GM’s machine connected to a server.

In reality, there were about 10 seats with a couple of laptops needed in the mix. From there, they need at least two new workstations, Remote Web Workplace connectivity was a must once demonstrated for key folks, Office 2007 licensing was needed for most of their desktops and laptops, AntiVirus, a firewall, and more.

So, where does that leave us? At a very distinct advantage to put together an awesome solution around Small Business Server 2008, Intel Server Hardware, Intel Workstation Hardware, a Microsoft Open Value Agreement for their licensing needs, and more!

Lesson to be learned?

  • Always be prepared to take the necessary extra steps to look into any opportunity that comes our way.

Sometimes those opportunities may seem like they are “not worth it”, but even the smallest of deals can be that seed sown that later pays off in the way of strong business relationships and business referrals.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Saturday, 13 June 2009

Office 2003 Won’t Uninstall when Deploying Office 2007 via Group Policy

After verifying that the workstations we have upgraded to Windows Vista Enterprise took the operating system without errors, we initiated an Office 2007 Professional Plus deployment via their SBS 2008 server.

In this case, we ran into a bit of a struggle with the existing Office 2003 setup.

In this particular network, the client was migrated to SBS 2008 via the Microsoft method about a month ago. The SBS 2003 box has since been repurposed.

For some strange reason, the Office 2007 install routine was not removing Office 2003 which is its default behaviour.

We were able to make sure that our Group Policy deployment was functioning as it should because one of the 9 workstations refused to upgrade to Windows Vista Enterprise (previous blog post) so we fresh installed the machine and it took the Office 2007 deployment without a problem.

When we tried to manually remove the Office 2003 install via Windows Vista’s Programs and Features menu, we were presented with a request for the PRO11.MSI file with the path pointing to \\OLD-SBS\ClientApps\Office2003Pro\PRO11.MSI.

So, out came the handy Windows Installer Clean Up Utility that we used to remove any reference to the Office 2003 install. From there, we removed the shortcuts in the start menu and ran a GPUpdate /force on the workstations.

After a reboot we were in business with the exception of one workstation where the Clean Up utility was run after Office 2007 was installed on it. Outlook was taken out by the utility so we needed to run the Office repair to fix it.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*All Mac on SBS posts will not be written on a Mac until we replace our now missing iMac! (previous blog post)

Windows Live Writer

Wednesday, 8 April 2009

SharePoint Designer 2007 – Free for Download

SharePoint Designer 2007, the product used to customize SharePoint v3 and Microsoft Office SharePoint Server, is now a free download. Note that registration will be required to gain access to it.

While we are by no means experts in SharePoint here at MPECS Inc. having SharePoint Designer available for use in our SBS installations has been very beneficial.

A good book that can be helpful with getting to know the ins and outs of working with SharePoint technologies via SharePoint Designer 2007 is the:

This is, in our opinion, a good move on Microsoft’s part. Though we hope that making the product free does not spell its demise.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*All Mac on SBS posts will not be written on a Mac until we replace our now missing iMac! (previous blog post)

Windows Live Writer

Friday, 27 February 2009

Configure the Business Contact Manager Database on SQL Server 2005

For those looking to improve their Business Contact Manager’s performance, the BCM database can be installed and configured on SQL Server.

The catch initially was that Outlook and BCM needed to be installed on the machine too. This is not really a good practice for a server.

The BCM team has given us a tool to accomplish the task without the need to install Outlook and BCM on the server: Outlook 2007 with Business Contact Manager: Database Admin Tool.

Note that the database server needs to be SQL 2005 SP2 32bit or SQL Express 2005 SP2 32bit and needs to have .NET 2.x installed.

Some further reading from the source:

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

Thursday, 26 February 2009

Outlook 2007 Cumulative Updates via KB 968009 Released - “Performance Patch”

A new cumulative update for Outlook 2007 has been released. This release will also be a part of the upcoming Office 2007 Service Pack 2.

The base article is here: MS KB 968009: Outlook 2007 improvements in the February 2009 cumulative update.

There are two Hotfix downloads indicated in the above KB article:

  • MS KB: 961752 (http://support.microsoft.com/kb/961752/ ) Description of the Outlook 2007 hotfix package (Outlook.msp): February 24, 2009.
  • KS KB: 967688 (http://support.microsoft.com/kb/967688/ ) Description of the Outlook 2007 hotfix package (Outlook-en-us.msp): February 24, 2009.

The first one has a large number of fixes included in it while the second one is specific to using keyboard shortcuts to cut and paste in a custom form.

We have applied the first hotfix since it is applicable here. The performance improvements seen in Outlook 2007 are tangible. Clicking through various high content volume folders is noticeably quicker as is the search feature for both contacts and for content within the folders themselves.

The first hotfix will require a reboot of the system even though we had Outlook and any TSRs shut down during the update.

Once the system came up after the reboot and Outlook was started, this is what we were greeted with:

09-02-26 Outlook 2007 post 961752

Outlook 2007: Preparing Outlook for first use.

The above process did indeed take enough time to refill the tea cup and get a couple of needed phone calls in!

Make sure to have a backup of your PST/OST/Mailbox prior to running any Outlook updates!

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

Monday, 25 August 2008

SBS 2003 Open Value License Part Numbers

Any clients we are picking up or upgrading we are putting into an Open Value License with the 3 year spread payment option.

Here are some Open Value license + Software Assurance part numbers for you:
  • T75-00927: SBS 2K3 Premium with 5 CALs
  • T74-01746: SBS 5 User CAL Pack
  • P73-01420: Windows Server 2003/8 Standard

Office 2007:

  • 269-09046: Office 2007 Pro Plus
  • 269-09061: Office 2007 Pro Plus Software Assurance ONLY (for clients with Licenses)
  • W87-00356: Office 2007 Small Business Edition
  • 021-07257: Office 2007 Standard
  • 076-03395: Office Project Standard 2007

Desktop OS:

  • 66J-01418: Vista Business with Vista Enterprise Software Assurance Up + SA.
  • WSB-00073: Microsoft Desktop Optimization Pack (shown per month - need 12/seat)

System Center Essentials:

  • UCH-00357: Microsoft System Center Essentials - license & software assurance
  • DJA-00834: Microsoft System Center Essentials Server Management License - license & software assurance
  • 4PX-01112: Sys Cntr Essntls ClientML Sngl Lic/SA Pack OLV 20 NL 1YR Acq Y1 Promo
  • A5S-00457: Microsoft System Center Data Protection Manager - License & software assurance - 1 server - additional product, 1 Year Acquired Year 1 - Open Value - Win - English
  • CVA-00079: Microsoft System Center Data Protection Manager Standard Server ML - License & software assurance - 1 operating system environment (OSE) - additional product, 1 Year Acquired Year 1 - Open Value - Win - Single Language
  • SNA-00274: SYST CTR VRTL MACH MGRWGE SNGL LIC/SA PACK OLV NL 1YR ACQ Y1 PROMO
Remember, right now the best value on the planet for our clients is an Open Value Agreement on their new SBS 2003 purchase.

What client is going to argue with a substantially reduced price for the upgrade:
  • Included
  • Free
  • Aux Gratis
  • Etc ...
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.

Monday, 11 August 2008

Business Contact Manager - Recovery via *.mdf and *.ldf only

We have a relatively new client that has been going through what is turning out to be a month long odyssey of getting their Lenovo X61 tablet working again.

After an initial diagnosis that the hard drive was failing, they made a backup of their data and the Lenovo on-site people showed up and swapped out the drives.

Two hard drives and three motherboards later, we need to get their Business Contact Manager (BCM) data back online.

One slight gotcha though: The only data we have to work with is the original MSSmallBusiness.ldf and MSSmallBusiness.mdf files.

How did we realize that we were facing a gotcha? When we went to import the data via the database management in BCM it did not give us the option to import a *.mdf file.

After some searching about, we came up with the following Business Contact Manager Team Blog post: Restoring a BCM database from SQL .mdf and .ldf files (Windows Vista or XP).

Noting comments in the post about the environment variable used in the script were for Vista, we made sure to point them to the physical files using the full path.

No matter how many ways that script was modified to get it to work, we could not get those files to mount.

This left us in a bit of a pickle. How do we proceed?

Note the command line structure in the script itself. It contains osql commands. And, we SBSers all know where we need the osql commands (previous blog post on taming SQL's memory usage) don't we?

A quick search for sql 2005 sp_attach_db leads us to: MS KB 224071: How to move SQL Server databases to a new location by using Detach and Attach functions in SQL Server.

Since our BCM database is already detached, we need only attach it again.

But, before we try that, we remove BCM off the system altogether.

After making sure that BCM was fully removed from the system, we reinstalled it.

Run services.msc to verify that the MSSSQL (MSSMLBIZ) database instance is up. Do not run Outlook yet because the BCM will try and initialize a new database during its setup phase.

The databases would be located in: C:\Documents and Settings\%username%\LocalSettings\Application Data\Microsoft\Business Contact Manager\MSSmallBusiness.mdf.

We copied the recovered database and log files into the above location.

From there, we ran the following at the command line (assume Enter after each line):


  1. hostname (system will reply with the name of your computer)
  2. osql -E -S MyComputer\MSSMLBIZ (assume MyComputer is your hostname)
  3. use master
  4. go
  5. sp_attach_db 'MSSmallBusiness','C:\Documents and Settings\Administrator\Local Settings\Application Data\Microsoft\Business Contact Manager\MSSmallBusiness.mdf','C:\Documents and Settings\Administrator\Local Settings\Application Data\Microsoft\Business Contact Manager\MSSmallBusiness.ldf'
  6. go
  7. quit
Note that osql can be run from within the database folder because the SQL binn folder resides in the System Path.

Once we had a successful database and log file attach to the MSSMLBIZ instance and fired up Outlook, all of the BCM content was there.

We then imported the recovered PST file and our client was good to go.

UPDATE 2008-10-15: If you get an access denied error on the attach attempt then BCM is not installed properly. Run BCM, create a new set of dbs (generally MSSmallBusiness2), and then uninstall BCM, copy the original dbs into the directory, and attach again.

If you need help recovering your databases, please drop us a line: BCM Recovery.

UPDATE 2008-11-03: Added the hostname step to make sure you find the correct system name.

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.

Monday, 28 July 2008

SBS - Companyweb and Office 2007 Documents

When there is a need to setup document libraries for Office 2007 documents, the current SBS SharePoint V2 Companyweb site does not know what to do with them.

To get that fixed, David Overton has an excellent post: How to get Companyweb (Windows SharePoint Services v2) to work with Office 2007.

Take note that one will need to run the following on each workstation, XP or Vista, that will access the Office 2007 documents on Companyweb:
reg add HKCU\Software\Microsoft\Office\12.0\Common\Internet /v OpenDocumentsReadWriteWhileBrowsing /t REG_DWORD /d 01
This command is via David's post, but must be emphasized as the Office 2007 documents will always open in Read Only mode without it.

As per David's post which links to the following Knowledgebase article: KB 870853: Office 2003 and 2007 Office documents open read-only in Internet Explorer.

David, thanks for sharing that. It has come in very handy!

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.

Monday, 21 April 2008

Office 2007 OEM Part Numbers

Here is a list of the common Office 2007 OEM single pack versions we deal with:
  • S55-02515 Office Basic 2007
  • 79G-01153 Office Home and Student 2007
  • 9QA-01757 Office Small Business Edition 2007
  • 269-14071 Office Professional Edition 2007
We tend to stick with purchasing the singles since the discount per copy when purchasing the three pack is only pennies. For smaller shops like us there is no sense tying up capital in stock that may sit on the shelf for a period of time.

If purchase volumes demonstrate the need for three packs, then here are the part numbers:

  • S55-02516 Office Basic 2007 (3 Pack)
  • 79G-01154 Office Home and Student 2007 (3 Pack)
  • 9QA-01758 Office Small Business Edition 2007 (3 Pack)
  • 269-14068 Office Professional Edition 2007 (3 Pack)
Up to date part numbers along with geographically specific ones can be had from the Microsoft OEM Partner site.

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.

Friday, 28 March 2008

Excel - Clean Up the Div/0 Errors in a Worksheet

We are setting up some custom quoting setups in Excel.

One formula that we have is: D20/E20.

If nothing is in the respective cells we get an error: #DIV/0!

Excel does not like to divide by zero.

To correct the error, we need to use a conditional formula on top of the above. We use the following Macro to change all of the affected cells:

Dim rng As Range, cell As Range, fmla As String
Set rng = Cells.SpecialCells(xlCellTypeFormulas, 16)
For Each cell In rng
fmla = Right(cell.Formula, Len(cell.Formula) - 1)
cell.Formula = "=if(iserror(" & fmla & "), """"," & fmla & ")"
Next
The procedure is as follows:
  1. Click on the Office Jewel and then the Excel Options button
  2. Find and check "Show Developers tab in the Ribbon"
  3. OK
  4. Click the Developer tab
  5. Click Macros
  6. Type a name: CleanUpDiv0 [Enter]
  7. Click Edit
  8. Paste the above Macro in between the Sub and End Sub lines.
  9. Close MS Visual Basic (should save automatically)
  10. Click the Macros button
  11. Make sure the CleanUpDiv0 is selected and click Run
The Div/0! errors will now be gone!

A screenshot of a properly formatted macro in MS Visual Basic:

Excel Clean Up Macro

This tip comes to us courtesy of Escalus near the bottom of the page on the MrExcel.com site: #Div/0.

One can also bring about the same results in Excel 2003 via the Tools menu.

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.

Monday, 28 January 2008

Outlook 2003 - Error - MAPI32.DLL is corrupt or the wrong version.

We were working with a client system that had a copy of Office 2007 Trial on it.

We removed the trial version of Office. After Office 2007 was uninstalled and we went to start Outlook 2003 we ended up with:


Microsoft Office Outlook

Cannot start Microsoft Office Outlook. MAPI32.DLL is corrupt or the wrong version. This could have been caused by installing other messaging software. Please reinstall Outlook.
Note that the error message indicates that we are supposed to reinstall Outlook. So, we ran a repair and then a reinstall of Office 2003 Professional both of which did not work.

After searching around for a fix, we came up with the following Microsoft Knowledgebase article: KB926196: Error message when you try to start Outlook 2003: "MAPI32.DLL is corrupt or the wrong version".

Here is the proper fix:
  1. Start Windows Explorer.
  2. Locate and then open the following folder on your computer: C:\Program Files\Common Files\System\Msmapi\1033
  3. Right-click the MSMapi32.dll file, and then click Rename.
    • Note The file (Msmapi32.dll) that you are renaming differs from the file (Mapi32.dll) that is mentioned in the error message.
  4. Type Msmapi32.old, and then press ENTER to rename the file.
  5. Start Outlook 2003.
The above method worked.

And, we have learned a little lesson here: A little time invested in searching out the error would have saved us the repair/reinstall time and had our client up and running a lot quicker.

It also reminds us that product error messages can be quite situational and time limited in their orientation. When the above message was written into Outlook 2003, the possible conflicts caused by Office 2007 were unknown to the product teams.

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.

Monday, 21 January 2008

Office 2007 Suite Grid - What is in what again?

It is a perennial question that all I.T. professionals get: "What is in what version of Office please?"

Here is a screenshot of the Office 2007 Suite product comparison grid:

Office 2007 Suites Comparison Grid

The original grid can be found here: 2007 Microsoft Office System suites.

Note that the step from Small Business Edition to Professional Edition is Microsoft Access. Since those are the most popular non-licensing versions we deal with, that is a good thing to remember.

Also, when selling OEM versions, we make a point of informing our clients that there is no accompanying media with OEM licenses and that it comes installed on a new system before the system leaves our shop. They can then order a copy of the media via a Web link in the license case for a small shipping fee.

Here is a link to our previous blog post on Windows Vista's editions: Windows Vista - Now ... Just Exactly What is in What Edition Again?!?

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.

Saturday, 22 December 2007

Office 2007 - Config.xml Error - Whitespace is not allowed at this location.

For those of us with absolutely no HTML/XHTML/XML coding experience, we may run into a bit of a headache when setting up Office 2007 to install via Logon Script and Group Policy.

We may see this when proofing the Config.xml file located in the source file directory ..\OfficeVersion.WW\Config.xml:

The XML page cannot be displayed

Cannot view XML input using XSL style sheet. Please correct the error and click the Refresh button, or try again later.




Whitespace is not allowed at this location. Error processing resource 'file ://mysbsserver/clientapps/office2007ent/...

Note the dotted line under the last line in the original image: ----------^

It is pointing to the space just after the actual cause of the problem.

What we need to remember is the file is coded in XML. Therefore, we need to follow XML coding rules when trying to insert special characters like the '&' ampersand in the above example.

Here is what the raw source code looks like:

Config.xml Source Code - Wrong

You can see that there is an actual '&' ampersand in the COMPANYNAME value.

A list of the codes needed for special characters like the '&' ampersand can be found here at Wikipedia: List of XML and HTML character entity references.

This is what the XML code should look like:

Config.xml Source Code - Correct

Note the "&" Ampersand+amp+Semicolon in the COMPANYNAME value. This code value will cause the XML to be rendered correctly.

Thus, after double clicking on the config.xml file, in IE you will see:

XML Correctly rendered in IE

For a complete explanation of the various settings in the config.xml file go here: TechNet: Config.xml in the 2007 Office system.

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.

Tuesday, 11 December 2007

Microsoft Office 2007 - OPK Kits For Free (3 Only) via MS OEM Site

Folks, the original Office 2007 Basic, Small Business, Professional, and Home & Student OPK kits that we could get through our suppliers here for less than $10 each are no more. That reduced rate was some sort of introductory offer.

The part number, if you can find it was: 269-11458.

The OPK part number that now has a royalty attached to it is:
  • 269-13607 for Canadian English
  • 269-13608 for Canadian French.
  • Supplier search key words:
    • Office 2007 OPK
    • Microsoft OEM OPK
    • 2007 OPK
    • Basic SB Pro OPK
Our suppliers here in Canada have at least a few of the above key words in their descriptions. Part numbers and search terms may vary relative to your particular geographical/language area.

There is one other offer that one can take up via Microsoft's OEM Web site: Order 2007 Microsoft Office OEM Preinstallation Kit (OPK) Master Kits. Note that if a company is not registered with the OEM site, then one will need to complete the registration process before obtaining the kits.

A company is allowed to order 3 free copies of the kit before being referred to an authorized distributor to purchase the royalty based discs.

For those clients that insist on getting media with their OEM license, they can order a backup media copy from here: Microsoft Office system backup discs for medialless license kits.

NOTE: The client will be required to provide their OEM install key to complete the order for backup media. And, the offer expires 90 days after the purchase of their system or systems.

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.

Monday, 15 October 2007

Outlook 2007 - RSS feeds no longer work ... period! 0xB7AC0008

Usually when the RSS feeds being aggregated in Outlook no longer feed in, a reboot fixes it.

Well, several reboots later, nothing seems to be working.

Outlook keeps throwing 0xD07C0008, 0xD28C0008, 0xD49C0008, 0xD6AC0008, and so on, and so on, ad infinitum.


This is Outlook 2007 on Vista x64 connected to our SBS Exchange server.

So, the next step is to export all of the feeds, then import them again. Nope. Doesn't work.

So, what are the options from there? One is to delete them one by one. Then, import the OPML file again. What a tedious process. There is a very painful pause in between each one. This is oh so senseless.

So, after all of this, Outlook is pretty much unresponsive. This is after deleting two of the blog feeds. There is not enough time in the day to fix it.

So, time to throw in the towel. Are there any good RSS Readers that integrate into Outlook 2007? Or, perhaps a standalone reader. Free is not so important as the ability to sort the feeds by blog and perhaps a further sort by subject would be nice.

*sigh*

Okay, maybe I spoke too soon. Outlook seems to have recovered. I was able to delete the feeds in both IE and Outlook, and the feeds are coming back with no errors - or at least some of them are. Time will tell if they pick up or not.

This breakage is cyclic. There seems to be no rhyme or reason behind it. But, it just keeps happening!

The question above still stands though. Time to move on until Microsoft gets their collective Outlook stuff together and fixes the problem.

Previous post on the subject: Outlook 2007 - RSS Broken Feed Frustration.

UPDATE: As I sit here, there are no RSS feeds coming up. Anything that showed up stopped on the date, October 10 or thereabouts, that things stopped working. So, no fix. :(

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.

Saturday, 6 October 2007

Office 2007 Action Pack Version Not GP Deployable?

We are in the process of working out the new methodology for delivering Office 2007 to the desktop via Group Policy.

We have a number of clients that are on Microsoft Licensing for their products.

Once we figured out how to set things up and run the GP install via startup script, we went to run an organization wide install for our company. Our Microsoft Action Pack (MAPS) covers this, so why not use the media that came with?

When we went to create our .MSP file for the logon script based deployment, we were greeted with the following error message:

Setup Error: Files Necessary to run the Office Customization Tool were not found. Run Setup from the installation point of a qualifying product.

Well, supposedly this is a qualifying product? We were able to deploy our MAPS version Office 2003 Professional via Group Policy with no issues.

According the the post at the Partner Blog Community: Office 2007 Retail version included in Action Pack? which is dated in February of 2007, this is a known "issue". The following link on that page goes to the Office public newsgroups where one would need to search for more specific answers.

We really are not sure what to say at this point. While the Microsoft Action Pack is valuable for us as a small company, the changes that seem to have come down as far as product licensing can be a bit puzzling to muddle through. This one, a retail versus OLP version for Office 2007 Enterprise, was not mentioned in any of the product documentation that we can see?

For those of us who run small but very busy shops, taking the time to manually install Office 2007 on the up to 10 systems as per the number of MAPS licenses is quite a hit for the whole organization.

Ultimately, before that change happened, those that utilize MAPS should have been consulted about the change. Whether by email, which we never received as far as we can see here, or even the Partner Action Pack Newsgroups, it would have been appropriate to ask those who would be impacted by any changes made.

Think MAPS Windows Vista upgrade version situation. From the MAPS Standard Contents page:
**In the United States, Microsoft will provide the UPGRADE version of the Windows Vista desktop operating system within Action Pack, which is consistent with how this product is distributed to our Volume Licensing customers.
For those of us who have had our MAPS for many years, there were no indications in any documentation to indicate we were receiving upgrade versions of Windows 2000 Professional or Windows XP Professional. They were indeed full versions, and could be installed as full versions as far as we understood our licensing and the EULA.

If anything, all of the confusion succeeded in clarifying many things about the Action Pack and our many misconstrued ideas as to what was included and how those products were licensed: In conclusion, we are faced with yet another inconsistency. The Vista note above indicates OLP as the licensing model, yet we have Retail, or Fully Packaged Product, in our hands for Office.

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.

Thursday, 23 August 2007

PowerPoint 2007 - Still buggy?!? - Slideshow Hangs...

We were requested to put together a slide show for a client. We decided to take PowerPoint 2007 for a test drive.

We ended up with a 25 panel slide show with multiple images and themes. We created a soundtrack for it on the Mac that ran the entire duration of the slide show.

We set the transition times for every panel to 15 seconds. We set the proper animation sequences for all of the panels and away we go right?

After saving the presentation in both presentation and slide show format, we took it for a test run.

Well, the first slide shows up, the music starts, then the second slide comes in 15 seconds later as expected. Then, it just hangs there. The slides no longer change. The second slide just sits there. The music keeps running though.

Okay, go back into the presentation, change the order of the slides to see if it is that particular slide, regenerate the slide show and try again.

Nope. It didn't work. Build a whole new slide? Nope, same thing happens again.

We still had a hang at the second slide.

So, the next step was to go back and see what happened to the transition settings. Each panel was still showing the 15 second transition time with the exception of the second one. It had 456:30:00 as a time setting!

Um, just where did that come from?

So, reset all of the panels to a transition time of 15 seconds, regenerate the slide show, and sure enough, it worked.

This was not an isolated incident. That 456:30:00 number showed up again, randomly, over the process of building the entire slide show.

Buried somewhere in PowerPoint, is that strange time number that only shows itself occasionally.

So, we learned a valuable lesson. Make sure that slide show works as expected before sending it off to the client.

Oh, and the soundtrack will, by default, be linked in the presentation so one should make sure to have the soundtrack mp3 accompany the final slideshow.pps or slideshow.ppsx.

By the way, the end user does not need to have PowerPoint installed on their system to run the slide show. They only need the PowerPoint Viewer. It can be found here: PowerPoint Viewer Download.

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.