The confugration wizard was generating the following error:
Date: 12/10/2008 00:23:47
Application: System Center Essentials
Application Version: 6.0.1251.0
Severity: Error
Message:
: Verification failed with [1] errors:
-------------------------------------------------------
Error 1:
: Failed to verify Override [OverrideForRuleMicrosoftSystemCenterEssentialsInternalScheduledDiscoveryForContextMicrosoftSystemCenterRootManagementServer6c1cc55796f6477f97fbe53bcdb1154f].
Override [OverrideForRuleMicrosoftSystemCenterEssentialsInternalScheduledDiscoveryForContextMicrosoftSystemCenterRootManagementServer6c1cc55796f6477f97fbe53bcdb1154f] is a duplicate to Override [OverrideForRuleMicrosoftSystemCenterEssentialsInternalScheduledDiscoveryForContextMicrosoftSystemCenterRootManagementServere2f7dfce1adc45e0adbcbf63664743af] defined within the same ManagementPack. Please remove any one of the duplicate overrides.
-------------------------------------------------------
Failed to verify Override [OverrideForRuleMicrosoftSystemCenterEssentialsInternalScheduledDiscoveryForContextMicrosoftSystemCenterRootManagementServer6c1cc55796f6477f97fbe53bcdb1154f].Override [OverrideForRuleMicrosoftSystemCenterEssentialsInternalScheduledDiscoveryForContextMicrosoftSystemCenterRootManagementServer6c1cc55796f6477f97fbe53bcdb1154f] is a duplicate to Override [OverrideForRuleMicrosoftSystemCenterEssentialsInternalScheduledDiscoveryForContextMicrosoftSystemCenterRootManagementServere2f7dfce1adc45e0adbcbf63664743af] defined within the same ManagementPack. Please remove any one of the duplicate overrides.
: Failed to verify Override [OverrideForRuleMicrosoftSystemCenterEssentialsInternalScheduledDiscoveryForContextMicrosoftSystemCenterRootManagementServer6c1cc55796f6477f97fbe53bcdb1154f].
Override [OverrideForRuleMicrosoftSystemCenterEssentialsInternalScheduledDiscoveryForContextMicrosoftSystemCenterRootManagementServer6c1cc55796f6477f97fbe53bcdb1154f] is a duplicate to Override [OverrideForRuleMicrosoftSystemCenterEssentialsInternalScheduledDiscoveryForContextMicrosoftSystemCenterRootManagementServere2f7dfce1adc45e0adbcbf63664743af] defined within the same ManagementPack. Please remove any one of the duplicate overrides.
: Override [OverrideForRuleMicrosoftSystemCenterEssentialsInternalScheduledDiscoveryForContextMicrosoftSystemCenterRootManagementServer6c1cc55796f6477f97fbe53bcdb1154f] is a duplicate to Override [OverrideForRuleMicrosoftSystemCenterEssentialsInternalScheduledDiscoveryForContextMicrosoftSystemCenterRootManagementServere2f7dfce1adc45e0adbcbf63664743af] defined within the same ManagementPack. Please remove any one of the duplicate overrides.
I found this closed bug:
http://connect.microsoft.com/OpsMgrFeedback/feedback/ViewFeedback.aspx?FeedbackID=286212
(Didn't help)
Then I found this, which did...
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2253298&SiteID=17
After an install of SCE 2007, the OpsMgr service would not start and kept throwing an 0x80004005 error.
Found another blog with a fix:
http://blogcastrepository.com/blogs/brian_tucker/archive/2008/01/16/scom-opsmgr-2007-health-service-error-0x80004005-event-id-7023.aspx
It was a little different in my case, I had to remove LMIRfsClientNP from the registry key:
HKEYLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder\ProviderOrder
After the install of Silverlight - My D-Link DCS-6620G camera started returning HTTP 400 Bad Request errors.
After a bit of investigation, I found this:
http://silverlight.net/forums/p/7452/77779.aspx
Locating the key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Accepted Documents, I removed a couple of XML document type I figured that I would never use.
Everything now works fine.
I'd forgotten this one... Something gets left in the registry so that the Kaspersky install keeps giving you this error:
"You must restart your computer before proceeding with the installation."
Download and apply this registry fix from Kaspersky.
More details here:
http://support.kaspersky.com/kolt/?eid=207694096
I've recently had an issue with my main desktop machine losing network connectivity overnight. No other machines are affected, only my desktop one. The problem computer is connected via wired ethernet to a Netgear GS105 Gigabit switch. The lights on the switch stay on, so there appears to be nothing wrong with the physical connection but the system still can contact nothing on the network.
What has worked as a fix, was to go into the network connections, disable and then enable the LAN connection. The computer will then work fine for another 24 hours.
After some searching, I read this:
http://forums.techarena.in/vista-help/791873.htm
Which then led to this:
http://support.microsoft.com/kb/927168
Now, each time the connection has stopped working, I have had my Windows Mobile 6.0 phone plugged in, synchronising and charging. I wondered if this was the same as Internet Connection Sharing as the phone is given an IP and can access the network via my desktop computer. When I had network problems with my network camera, I do remember switching on RSS (receive side scaling) as part of the changes made to the IP stack.
I've disabled RSS for now using the command:
netsh interface tcp set global rss=disabled
I'll followup with any further lockups or not!
I recently bought a D-Link DCS-6620G IP camera to replace a failed Panasonic one. I found the performance to be terrible. After running a network capture I discovered the following:
My Vista desktop would send two TCP SYN requests with ECN and CWR flags set.
The camera would resond to each of these with a TCP RST.
My Vista desktop would then send a TCP SYN request without ECN and CWR flags and the camera would then respond normally.
This problem also meant that I could not add the camera to D-Link D-ViewCam Monitor as the request to add a camera failed with an unable to connect message.
After a bit of reading, I discovered the CWR and ECN flags were being set because I had ECN enabled in my IP stack. I verified this by running:
netsh interface tcp show global
Querying active state...
TCP Global Parameters
----------------------------------------------
Receive-Side Scaling State : enabled
Chimney Offload State : disabled
Receive Window Auto-Tuning Level : disabled
Add-On Congestion Control Provider : none
ECN Capability : enabled
RFC 1323 Timestamps : disabled
Running the following, disabled the setting:
netsh interface tcp set global ecncapability=disabled
Ok.
And...
netsh interface tcp show global
Querying active state...
TCP Global Parameters
----------------------------------------------
Receive-Side Scaling State : enabled
Chimney Offload State : disabled
Receive Window Auto-Tuning Level : disabled
Add-On Congestion Control Provider : none
ECN Capability : disabled
RFC 1323 Timestamps : disabled
The camera is now working very well.
If you have multiple storage groups with the same data retention policies, you can now colocate the data on the same tapes as long as you have installed the DPM 2007 feature pack. Most useful if you have a single drive rather than a library.
It's not settable in the GUI, but the following Powershell command turns it on:
Set-DPMGlobalProperty -DpmServer <DPM Server Name> -OptimizeTapeUsage $true
More details here.
This (KB949870), was applied by Windows Update last night, and I woke up to no incoming email. On investigation, I found that there was no smtp (25) port open, and that the Microsoft Exchange Transport hadn't started after the reboot.
I attempted to manually start the service, but no joy as it timed out after 30 seconds. I reviewed the event logs, nothing there, tried again and it worked. Did a trawl back through the event logs when the server restarted, and again nothing. There were some eventid 3001\3003 from the EvntAgnt (log file not at end) so I may be missing some logs.
The only other issue I can think of, is that this is a single server Exchange 2007 installation - I.e. The transport service is running on the same server as the mailboxes rather than on a separate edge server. I would think this receives no testing by Microsoft!
I will have to monitor this the next time I reboot. Is anyone else having this issue?
I used the command:
"w32tm /config /manualpeerlist:"uk.pool.ntp.org europe.pool.ntp.org" /syncfromflags:manual /reliable:yes /update"
More details here:
http://technet2.microsoft.com/windowsserver/en/library/f3d6b66c-5fdc-4a77-a901-5efbcb4d4bb71033.mspx?mfr=true
I've been having an issue for some time where certain users and groups were having thier AD inheritance flag cleared and an arbitary set of permissions made.
It turns out that this is by design. Because the users belonged to a group, which belonged to Print Operators, thier permissions were being set to match the System\AdminSDHolder object. The PDC emulator runs an hourly process which copies the permissions from AdminSDHolder to these protected objects.
The following article describes how to remove Print Operators from this protected list of groups. The article talks about a hotfix, but this is only relevent for Windows 2003 SP1. Windows 2003 SP2 already has this change.
You can find the article here:
http://support.microsoft.com/kb/817433/en-us
Just wanted to share a couple of excellent Media Center addons I have found recently.
The first, called WebGuide4, allows you to access your Media Center PC through a web interface, including mobile:
http://www.asciiexpress.com/wiki/
The second allows access to BBC iPlayer, ITV Catch Up and Channel 4 Catch Up from within Media Center:
http://www.milliesoft.co.uk/index.php?option=com_content&view=article&id=9&Itemid=11
I recently modifed my DPM 2007 installation to backup my local users folder on Windows Vista Ultimate x64. This would not work and kept producing the following event logs when I attemted to manually sync the share:
Log Name: Application
Source: Application Error
Date: 15/06/2008 08:50:37
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Cartman2.thefoleyhouse.co.uk
Description:
Faulting application DPMRA.exe, version 2.0.5820.0, time stamp 0x46f990f7, faulting module kernel32.dll, version 6.0.6001.18000, time stamp 0x4791ada5, exception code 0x80070002, fault offset 0x000000000002649d, process id 0x1ff8, application start time 0x01c8cebaac1ac7c8.
After some research I found the following fix:
http://www.eggheadcafe.com/software/aspnet/31450629/cant-create-recovery-poi.aspx
You have to create the following DWORD registry key with a value of 1:
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\kernel\obcaseinsensitive
My Media Center PC randomly decided to stop working. After a lot of searching and trying I finally found this:
http://mymce.wordpress.com/2006/11/30/a-component-registration-failurea-critical-process-failurea-tuner-not-found-error/
The steps were:
- Close Media Center
- Click on the Start menu, choose run and type cmd
- Execute the command regsvr32.exe atl.dll
- Execute the command C:\WINDOWS\eHome\ehSched /unregServer
- Execute the command C:\WINDOWS\eHome\ehSched /service
- Execute the command C:\WINDOWS\eHome\ehRecvr /unregServer
- Execute the command C:\WINDOWS\eHome\ehRecvr /service
- Execute the command C:\WINDOWS\eHome\ehRec.exe /unregServer
- Execute the command C:\WINDOWS\eHome\ehRec.exe /regserver
- Execute the command C:\WINDOWS\eHome\ehmsas.exe /unregServer
- Execute the command C:\WINDOWS\eHome\ehmsas.exe /regserver
- Restart Media Center
Thanks so much guys!
After rebooting my Exchange server because of DNS issue, the DPM protection stopped. Further investigation found this in the event log:
The DPMRA service terminated with service-specific error 10048 (0x2740).
Google found this:
http://support.microsoft.com/kb/947682
Essentialy you use 'netstat -oan' to find the PID of the process using port 5718 or 5719, which are both required by DPMRA.
Then use 'tasklist' and 'tasklist /svc' to discover which process it is. In my case, it was the MS Exchange Information Store.
I fixed it by stopping all Exchange services, starting DPMRA and then restarting Exchange.
It's kind of weird that MS Exchange can use the DPMRA ports when DPM is speciffically for protecting Exchange (amongst other things).