Re: error - OfficeUpdate.MOF not generated, some problem with Scan tool
From: Adam Welker [MSFT] (adamwel_at_online.microsoft.com)
Date: 07/08/04
- Next message: Adam Welker [MSFT]: "Re: Scan Failures on SMS Client"
- Previous message: Steven van Houttum: "Re: MOFMAN for SMS 2003?"
- In reply to: Highland: "Re: error - OfficeUpdate.MOF not generated, some problem with Scan tool"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 8 Jul 2004 08:18:41 -0700
Ok. I see the issue now. The best course of action for you would be to
contact PSS. As this appears to be a "bug" I don't think there is any cost
associated with said call, but you should probably verify that when you call
in. Tell the SMS support report to contact me if they have any questions.
-- Adam Welker This posting is provided "AS IS" with no warranties, and confers no rights. "Highland" <anonymous@discussions.microsoft.com> wrote in message news:27dfb01c46450$d1a94830$a601280a@phx.gbl... > A bit more detail on what we've seen: > > We have the exact same issue. In our case we have an "&" > in our domain name (Created before my time here). > > The issue is specifically related to the MSBA portion of > the scan. I have run the baseline analyzer as a > standalone application and I have the same exact issue. > If you edit the XML and tweak the code to include "apm;" > after the ampresand in the <DOMAIN> section, the issue > goes away. > > As you can probably see, this is simply not feasable in > the SMS-SUS scenario due to the sheer # of clients, and > the fact that MSBA is integratedinto the SUS via code. > > Any suggestion you may have would be greatly appreciated. > > > >-----Original Message----- > >"Adam Welker [MSFT]" <adamwel@online.microsoft.com> wrote > in message news:<#WAN0J#UEHA.2544@TK2MSFTNGP10.phx.gbl>... > >> Would you mind posting that special character for me? > > > > > >I have this exact same issue. The issue goes beyond > SMS. It is a BUG > >in the MBSA. In my case we have an ampersand in ourt > domain name (&). > > > >If any form of resolution is found, please post it here, > or put it out > >as a SP for the tool(s) > >. > >
- Next message: Adam Welker [MSFT]: "Re: Scan Failures on SMS Client"
- Previous message: Steven van Houttum: "Re: MOFMAN for SMS 2003?"
- In reply to: Highland: "Re: error - OfficeUpdate.MOF not generated, some problem with Scan tool"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|