If you try to open the OpsMgr console, you may get such an error:

Date: 9/12/2013 11:52:41 AM
Application: Operations Manager
Application Version: 7.0.8560.0
Severity: Error
Message: Failed to connect to server 'MSname'
Microsoft.EnterpriseManagement.Common.UnknownServiceException: The service threw an unknown exception. See inner exception for details. ---> System.ServiceModel.FaultException`1[System.UnauthorizedAccessException]: The creator of this fault did not specify a Reason.
Server stack trace:
at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.EnterpriseManagement.Common.Internal.IDispatcherService.Connect(SdkClientConnectionOptions connectionOptions)
at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.Initialize(EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService)
at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.CreateEndpoint[T](EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService)
--- End of inner exception stack trace ---
at Microsoft.EnterpriseManagement.Common.Internal.ExceptionHandlers.HandleChannelExceptions(Exception ex)
at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.CreateEndpoint[T](EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService)
at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.ConstructEnterpriseManagementGroupInternal[T,P](EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore clientCallback)
at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.RetrieveEnterpriseManagementGroupInternal[T,P](EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore callbackDispatcherService)
at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.Connect[T,P](EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore callbackDispatcherService)
at Microsoft.EnterpriseManagement.ManagementGroup.InternalInitialize(EnterpriseManagementConnectionSettings connectionSettings, ManagementGroupInternal internals)
at Microsoft.EnterpriseManagement.Mom.Internal.UI.Common.ManagementGroupSessionManager.Connect(String server)
at Microsoft.EnterpriseManagement.Monitoring.Console.Internal.ConsoleWindowBase.TryConnectToManagementGroupJob(Object sender, ConsoleJobEventArgs args)
System.ServiceModel.FaultException`1[System.UnauthorizedAccessException]: The creator of this fault did not specify a Reason. (Fault Detail is equal to System.UnauthorizedAccessException: You have exceeded the evaluation period of this product. Please upgrade to the retail version to continue using the product. For information on purchasing the retail version of this product, go to https://go.microsoft.com/fwlink/?LinkID=74446.
at Microsoft.EnterpriseManagement.ServiceDataLayer.SessionManagerService.CheckLicence()
at Microsoft.EnterpriseManagement.ServiceDataLayer.SessionManagerService.Connect(SdkClientConnectionOptions options)
at Microsoft.EnterpriseManagement.ServiceDataLayer.BasicDispatcherService.Connect(SdkClientConnectionOptions connectionOptions)).

Or this one in the Operations Manager events:

Log Name:      Operations Manager
Source:        OpsMgr SDK Service
Date:          9/12/2013 11:52:41 AM
Event ID:      26319
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      MSName
Description:
An exception was thrown while processing Connect for session ID uuid:5ab6d42f-8aaa-4893-9c58-de8c4298694c;id=4.
  Exception message: You have exceeded the evaluation period of this product. Please upgrade to the retail version to continue using the product. For information on purchasing the retail version of this product, go to https://go.microsoft.com/fwlink/?LinkID=74446.
  Full Exception: System.UnauthorizedAccessException: You have exceeded the evaluation period of this product. Please upgrade to the retail version to continue using the product. For information on purchasing the retail version of this product, go to https://go.microsoft.com/fwlink/?LinkID=74446.
   at Microsoft.EnterpriseManagement.ServiceDataLayer.SessionManagerService.CheckLicence()
   at Microsoft.EnterpriseManagement.ServiceDataLayer.SessionManagerService.Connect(SdkClientConnectionOptions options)
   at Microsoft.EnterpriseManagement.ServiceDataLayer.BasicDispatcherService.Connect(SdkClientConnectionOptions connectionOptions)

So the main reason why OpsMgr console is not opening is because we have exceeded the evaluation period of System Center 2012 Operations Manager.

Get your System Center Product key and follow the below steps to get your console open:

1. Run Windows PowerShell Modules as administrator

2. Run the following power shell cmdlet:

Import-Module OperationsManager

3. Then run the following cmdlet:

New-SCOMManagementGroupConnection

4. You might get the following error after running the command:

New-SCManagementGroupConnection : The service threw an unknown exception. See inner exception for details.
At line:1 char:34
+ New-SCOMManagementGroupConnection <<<<
+ CategoryInfo : InvalidOperation: (Microsoft.Syste...nnectionCommand:NewSCManagementGroupConnectionCommand) [New-SCManagementGroupConnection], UnknownServiceException
+ FullyQualifiedErrorId : ExecutionError,Microsoft.SystemCenter.Core.Commands.NewSCManagementGroupConnectionCommand

• This error is basically because the evaluation period already expired and hence we will not be able to connect to the Management Group. To workaround this, we need to change the date on the Management Server to a day where we were still in evaluation period. (1 or even 2 months back)
• Restart the System Center Data Access service and rerun the cmdlet New-SCOMManagementGroupConnection. It should work this time.

5. Then run the following cmdlet to see when the evaluation period expired:

Get-SCOMManagementGroup | ft skuforlicense, version, timeofexpiration –a

• Sometime this cmdlet hangs and does not show any result if the date is not changed back. You need to make sure the date is changed back and the System Center Data Access is restarted then repeat the above 4 steps again

Import-Module OperationsManager
New-SCOMManagementGroupConnection
Get-SCOMManagementGroup | ft skuforlicense, version, timeofexpiration -a

6. Then use the following command to enter your product key:

Set-SCOMLicense -ProductId "yourlicensekey“

7. Restart the System Center Data Access service and you should be able to open the console successfully by now

I hope you find this blog useful.

Waddah Shamroukh

Senior Support Engineer 

• Open OpsMgr Console and go to Authoring—> Management Pack Objects—> Rules
• Click on “Scope“ button in the tool bar to narrow down our selection.
• I assume the file is located on a windows computer, so we will search for “Windows Computer”
• Select Windows Computer and then click Ok

• Right click on rules and select “Create a new rule”
• Expand Alert Generating Rules—>Event Based—>Generic Text Log(Alert)

• In the above window click new to create a new management pack to save this new rule in it. In my case I have created a management pack called “TestRuleMP”
• In the next screen, give a meaningful name to this rule.
• The Rule Target should be Windows Computer
• Make sure to to uncheck the option “Rule is enable” before you proceed

• In the next screen provide the pattern of the file. If the file name is fixed and not changing every time the file is created, then you may give the exact name of the log as LogName.txt  but if the log file name is changing every time is created (LogFileName01, LogFileName02, etc..) then you may put the log file name as the following: LogFileName*.txt and then click next

• Now it is time to set your event expression to generate the alert .
• Click Insert so a new line will be added.
• In the parameter name write: Params/Param[1]
• In the operator select "Match wildcard”
• In the value put “?” – without quotes

• Proceed to configure the alert as the following:

A new Entry was detect in the c:\log\bader.log

Logfile Directory : $Data/EventData/DataItem/LogFileDirectory$
Logfile name: $Data/EventData/DataItem/LogFileName$
String:  $Data/EventData/DataItem/Params/Param[1]$

• Once you are done with editing the alert, click create.
• We have not enabled the rule yet so we need to override the rule and just enable it for a specific computer on which the log is located

• To reproduce the alert, I opened the log file and I typed a new line in it and saved the changes. See the below screenshot

• Now the alert is generated

You can notice that the alert description includes the new entry which was logged in the log file

Distribution Point فشل فى اضافة الحزم إلى

distmgr.log و وجود أخطاء في

NAL[1] - ERROR: failed to set the Security Descriptor for the object.  Access is denied. SMS_DISTRIBUTION_MANAGER 16-03-2010 10:39:01 1744 (0x06D0)
RDC:Failed to set access security on \\XXXXXX\SMSSIG$\Package$\XXXXX.tar for package 000004B1 signature file SMS_DISTRIBUTION_MANAGER 16-03-2010 10:39:01 1744 (0x06D0)
Cannot copy package 000004B1 from H:\_S Mxtz1.TMP\ to H:\Packages\SMSPKG\000004B1\, Win32 Error = 0 SMS_DISTRIBUTION_MANAGER 16-03-2010 10:39:01 1744 (0x06D0)
Failed to copy package 000004B1 from H:\_S Mxtz1.TMP\ to MSWNET:["SMS_SITE=R00"]\\XXXXXX\PACKAGE$\SMSPKG\XXXXX\ SMS_DISTRIBUTION_MANAGER 16-03-2010 10:39:01 1744 (0x06D0)

:السبب

عدم كفابة التصريحات على المجلد

\\servername\smssig$

:الحل

Everyone او system account توفر التحكم الكامل لكل

على المجلد

\\servername\smssig$

Eman

SCCM 2007 عند استخدام

PXE Boot فى

:لعملاء عبر الشبكات الفرعية قد تفشل العملية مع الأخطاء التالية

PXE-T04: Access Violation
PXE-E36: Error Received from TFTP Server
PXE-M-F Exiting PXE Rom

PXE Booting يمكن أن يحدث هذا عندما تحاول

Virtual Machine or Physical Machine من

SMSPXE.log كما قد تلاحظ عدم تكون الإدخالات في

"PXE Service Point Server "  على

PXE Booting من العملاء

PXE Service Point مما يشير إلى أن العميل لم يتصل ابدا فى

:السبب

DHCP يمكن أن يحدث هذا لمشكلة فى

IP Helper او يكون 

Router/Switch غير مشغل فى

:الحل

IP Helper – BOOTP قد تحتاج إلى تكوين إعدادات

Router على

DHCP أو تكوين خيارات النطاق

حسب اللازم

يمكن أن يحدث هذا أيضا إذا تم تكوين الإعدادات بشكل خاطئ

Eman

If I want to collect the security events of the agents in the DMZ/untrusted domain, there would be two approaches to achieve this goal, either by using the certificate based authentication as described in Clive Eastwood blog or installing the ACS role on the gateway server. Since the ACS collected to DB is one-to-one relationship, multiple ACS collector cannot connect to one ACS DB at the same time, yet you can have two collector connected to one ACS database if failover setup is in place, which means one of the collector is active and the other is offline. Furthermore, the ACS role cannot be installed on a workgroup gateway. Either you need to leverage the gateway into domain controller or at least be a member server of a domain.

I have the following lab: two domains where no trust relationship is available between them.

On the domain where the RMS is located, I have RMS, MS, and SQL cluster. The RMS is also a reporting and audit collector server. The OpsMgrDB, OpsMgrDW and OpsMgrAC DB are all located on the sql cluster.

The gateway is already configured with certificate authentication and reporting to the MS, I had just to install the ACS role on the gateway. Since the ACS collector on the gateway cannot connect to the same DB of the collector in the trusted domain, we have to create a new ACS DB either in the same domain of the gateway, or in the trusted domain of the RMS. In my example I preferred to install the ACS DB in the trusted domain on the same SQL

server.

Insert the OpsMgr 2007 media on the gateway server and select Audit Collection Service. In the first screen of the installation wizard, select “Create a new database”:

In the Data source screen, leave the default data source name as it is and click next

In the database screen, I have to point to the SQL Server (opsmgr-sql) in the trusted domain and give a different name for the database (OperationsManagerGWAC) since this SQL server is having the first ACS DB of the trusted domain (RMS domain)

In the database authentication screen, we will use the SQL authentication mode since there is no trust between the two domains. adtadmin is a SQL user i have created before on the SQL Server.

In the database creation screen, I had selected to use the default SQL Server data and log file directories, but unfortunately the installation of the ACS, was always failing

When I checked the SQL Server logs, the installation was trying to create the same data and log files of the first ACS DB!! So I have created a subfolder for the new ACS DB and re-run the ACS installation on the gateway, but this time i have to specify the DB data and log directories

In the SQL Server login name, I have provided the SA SQL account which will be sufficient to create the DB and its tables.

This time the installation of the ACS also failed but at least the all the steps were all successful except “Starting the AdtServer service”!!

I have tried to start the Operations Manager Audit Collection Service manually but it failed and the error was “Insufficient access rights to perform this operation”!!!

I checked the gateway OpsMgr log and found the following error:

The service was not able to start because it failed to register the SPN. So I realized I had to add the SPN’s manually on the computer account of the gateway. AdtServer/OPSMGR-GATEWAY and AdtServer/opsmgr-gateway.scom.opsmgr

After that i have tried to start the Audit collection service and this time started successfully.

I checked the gateway OpsMgr logs and all seem okay:

So now it is time to enable the audit collection service on the agent in the untrusted domain which is reporting to the gateway. In the OpsMgr console, go to Monitoring –> Operations Manager –> Agent –> Agent Health State. Select the agent in the untrusted domain and click on “Enable Audit collection” on the actions pane. Select Collection Server and then click on Override button to provide the FQDN of the gateway server(opsmgr-gateway.scom.opsmgr). In the Task credentials, provide a user name and password from the untrusted domain (gateway domain). Enabling the ACS on the agent was successful. I checked the logs of the agent and it was showing the agent successfully connected to the collector (gateway)

Now it is time to run the reports, but will I be able to run the Audit reports in the OpsMgr console against the agents in the untrusted domain? The answer is no!!! because the Audit reports data source is pointing to the ACS DB in the trusted domain (OperationsManagerAC), while the ACS database which we have just created is OperationsManagerGWAC. So what to do? Okay, first I have to change the name of the folder of the Audit reports in the SQL Server reporting services. I gave it this name “Audit Reports – Trusted Domain”, then I have uploaded the Audit reports which are included in the OpsMgr 2007 media CD. The reports were uploaded successfully, and they have the default name “Audit Reports”, so I decided to give it a better name “ Audit Reports – Untrusted Domain”.

Before running the reports against the agents in the untrusted domain (gateway domain), we need to make sure that the audit reports data source is pointing to the proper ACS DB as by the default when you upload the Audit reports, the data source is pointing to OperationsManagerAC DB. I have changed the database to the new created DB OperationsManagerGWAC and applied the settings

Now it is time to check if we have data or not. I ran the report “ Forensic – All Events For Specified Computer” and here we go, I got the following report