Jump to content


BogdanR

Established Members
  • Content Count

    13
  • Joined

  • Last visited

Community Reputation

0 Neutral

About BogdanR

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hey, Usually when you are out of space on C: your SCOM agent also stop. You can easily check this by opening the Services tab (services.msc) and verify the status of HealthService (Microsoft Monitoring Agent). Like I said before you can also check your status by opening the SCOM logs from Event Viewer -> Applications and Service Logs -> Microsoft -> Operations Manager. In the SCOM console you'll see two different alerts "Health Service Heartbeat Failure" and "Failed to Connect to Computer". That should give you an idea why your agent it's not working correctly. Seems that your SCOM environment it's not 100 % build for production so yea I guess re-install it seems like a good choice too :-) Cheers.
  2. Hello Michael, In a few words can you please explain what it's not working anymore ? I mean can you be more specific, it's a SCOM server related issue, an SQL one or did you already manually close all the alerts from the console :-) I'm trying to understand your SCOM environment first, to be able to provide the best answers to help you. Btw, one of the quickest ways to verify/debug your infrastructure it's to check the SCOM logs by opening Event Viewer -> Applications and Service Logs -> Microsoft -> Operations Manager. To answer your question, the only way of "going back" it's to restore an earlier back-up, if you are already protecting this SCOM server with a proper backup solution like EMC Networker, Symantec NETBackup, Microsoft DPM (Data Protection Manager) etc or if this SCOM server it's virtual, using an snapshot/checkpoint to revert to the initial one ( which personally I wouldn't recommend it in production environment from various reasons). And since we're talking about backup, please also check these 2 links: Microsoft: https://technet.microsoft.com/en-us/library/hh278864(v=sc.12).aspx https://technet.microsoft.com/en-us/library/hh278860(v=sc.12).aspx Blogs: https://stevethompsonmvp.wordpress.com/2013/06/07/sql-server-backup-recommendations-for-configuration-manager/ (I know it's for SCCM but the principle also applies to SCOM as well). Other then that, the other way should be to debug/repair it somehow but that requires some experience, patience & luck. Regards.
  3. Hey Michael, First, welcome to the SCOM world :-) I believe/assume you have the latest version which is SCOM 2012 R2 UR11, correct ? If not, please take a look here on how to upgrade your SCOM environment to the latest version: https://blogs.technet.microsoft.com/kevinholman/2016/09/06/ur11-for-scom-2012-r2-step-by-step/ Second, did you install SCOM into a test environment or directly into a production one ? Third, your SCOM server is installed along with the database server (SQL instance) or are you keep them separately ? The reason I'm asking is because it's better to keep them apart, with time the two SCOM DBs (OperationsManager & OperationsManagerDW) tend to put more pressure on your SCOM server and it would behave more slowly, especially working with the SCOM console. Fourth, did you already installed some of the SCOM agents on your environment ? SCOM requires the installation of an agent to be able to fully monitor a server/client. Of course there is also the possibility to choose an agentless way of monitoring devices, but for now it's not the case, it will put more pressure on your SCOM server, so stick with the agent way. Fifth, depending on what exactly are you trying to monitor, let's say for starter that you only need to monitor the servers (later you can easily monitor clients and network devices as well) you need to import a couple of basic MPs (Management or Monitoring Packs as MS likes to call them), here are some for you to start with: Windows Server Management Pack - https://www.microsoft.com/en-za/download/details.aspx?id=9296 Active Directory - https://www.microsoft.com/en-us/download/details.aspx?id=21357 DNS - https://www.microsoft.com/en-us/download/details.aspx?id=37141 DHCP - https://www.microsoft.com/en-us/download/details.aspx?id=39062 FileServer - https://www.microsoft.com/en-us/download/details.aspx?id=34970 SQL Server - https://www.microsoft.com/en-za/download/details.aspx?id=51645 CA (Certification Authority) - https://www.microsoft.com/en-us/download/details.aspx?id=34765 Of course there many others, depending on your infrastructure and requirements, here are some additional links: https://unofficialsystemcentercatalog.wordpress.com/2012/12/27/operations-manager-is-there-a-management-pack-for/ http://social.technet.microsoft.com/wiki/contents/articles/16174.microsoft-management-packs.aspx http://systemcentercore.com/ So, go ahead and install some of the ones I've just told you, and pretty soon you will see all kinds of critical, warning and informational alerts into your SCOM console :-) Now the fun begins, just give it a week or so until the SCOM environment will settle a little, and then begin to filter the messages. Be careful though that in SCOM world there are 2 types or alerts, some generated by monitors and other generated by rules, more info here (read them with attention because you don't want to ruin your environment already) : https://scomanswers.com/2015/03/04/scom-rule-vs-monitor/ http://www.culham.net/scom/scom-rules-vs-monitors/ http://blog.wouters.it/2009/04/scom-monitor-vs-rule.html Meanwhile be sure to check most of the SCOM blogs and official news from the MS OM team itself: Microsoft: https://blogs.technet.microsoft.com/momteam/ http://social.technet.microsoft.com/wiki/contents/articles/31909.ms-operations-management-suite-survival-guide.aspx http://social.technet.microsoft.com/wiki/contents/articles/20796.the-system-center-2012-r2-operations-manager-survival-guide.aspx Other valuable blogs: https://blogs.technet.microsoft.com/kevinholman/ http://www.opsman.co.za/category/scom-2012-r2/ http://kevingreeneitblog.blogspot.ro/ https://scomandothergeekystuff.com/ http://thoughtsonopsmgr.blogspot.ro/ http://www.bictt.com/blogs/bictt.php http://www.culham.net/category/scom/ https://stefanroth.net/ http://blog.tyang.org/ If you have any questions please let me know. Good luck :-)
  4. Hi, I have a simple application that I need to install, another old one which I need to uninstall it first and I need to make a registry change along with it. I chose to batch the process, and here’s what I have: Uninstall: msiexec /uninstall {19ED22B4-4058-4BB6-AFBB-357D6383534E} /quiet Install: Msiexec /q /i "\\fileserver\Source$ \Laserform_Intranet_Client_2.3\LFormInetClient.msi" SQLSERVER="Server" WEBSERVER="http://Server/LformInet/Default.aspx" DMSID="MHODMA" Update registry key: regedit.exe /s "%~dp0change.reg" The two registry keys looks like this: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Laserform\LFormInet] "SQL Server"="Server" "URL"="http://Server/LformInet/" "DBTYPE"="SQL" "SQL ServerLive"="Server" [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Laserform\LFormInet] "SQL Server"="Server" "DBTYPE"="SQL" "ClientVer"="5.1.33" In the end the .bat file should look like this: msiexec /uninstall {19ED22B4-4058-4BB6-AFBB-357D6383534E} /quiet Msiexec /q /i "\\fileserver\Source$ \Laserform_Intranet_Client_2.3\LFormInetClient.msi" SQLSERVER="Server" WEBSERVER="http://Server/LformInet/Default.aspx" DMSID="MHODMA" REM Check if 32-bit command-prompt launched on 64-bit OS IF "%PROCESSOR_ARCHITEW6432%"=="AMD64" SET REGPATH=%SystemRoot%\SysWOW64\REGEDIT.EXE %REGPATH% /s "%~dp0change.reg" So from what I understand so far (at least this is what someone explain it to me) it is possible that the registry edit won’t work if run through ConfigMgr though for two reasons. First, you are trying to modify a value specific to a user and second because you are trying to modify a value in the 32-bit section of the Software hive. Anyone have other experiences using something like this ? Thank you.
  5. Hello, I`m trying to upgrade from ConfigMgr 2012 SP1 CU5 to ConfigMgr 2012 R2 (and then CM 2012 R2 SP1 CU3) and during the upgrade wizard I receive the following error: “Setup failed to configure SQL Service Broker. Possible cause: Each Configuration Manager site must have its own SQL Server instance. Verify that the SQL Server instance is not in use by another Configuration Manager site” Looking into the ConfigMgrSetup.log I see these errors: INFO: SQL Connection succeeded. Connection: SMS_ACCESS, Type: Secure *** IF NOT EXISTS (SELECT * FROM sys.server_principals WHERE name='SQL02P\ConfigMgr_DViewAccess') BEGIN CREATE LOGIN [sql02P\ConfigMgr_DViewAccess] FROM WINDOWS END *** [42000][15025][Microsoft] [sql Server]The server principal 'SQL02P\ConfigMgr_DViewAccess' already exists. ERROR: SQL Server error: [42000][15025][Microsoft][sql Server Native Client 11.0][sql Server]The server principal 'SQL02P\ConfigMgr_DViewAccess' already exists. INFO: Executing SQL Server command: <IF NOT EXISTS (SELECT * FROM sys.server_principals WHERE name='SQL02P\ConfigMgr_DViewAccess') BEGIN CREATE LOGIN [sql02P\ConfigMgr_DViewAccess] FROM WINDOWS END> ERROR: ExecuteSqlCommand failed to execute IF NOT EXISTS (SELECT * FROM sys.server_principals WHERE name='SQL02P\ConfigMgr_DViewAccess') BEGIN CREATE LOGIN [sql02P\ConfigMgr_DViewAccess] FROM WINDOWS END, SQL error <> ERROR: Failed to create group for distributed view access. ~===================== Failed Configuration Manager 2012 Server Setup - Upgrade ===================== For the installation I`m using a domain administrator account with sysadmin privileges on the SQL Cluster where the CM database resides (2 nodes with Microsoft SQL 2008 R2 SP2 Standard without any Cumulative Update installed). I also checked the compatibility matrix CM-SQL https://technet.microsoft.com/en-us/library/gg682077.aspx and it seems that the minimum required SQL Server cumulative update is CU9 for my scenario, but I`m not sure that this is the real issue here. Of course the CM server is not working anymore, so the only option at the moment seems to be a restore, but I would like to find out why the upgrade failed. Any help would be greatly appreciated. Regards.
  6. Hello, I also experiencing the same issues with this particular model of laptop Dell Latitude E5450 trying to deploy Windows 8.1 Enteprise x64 using SCCM 2012 R2 CU2 along with MDT 2013. I succeed doing these steps: 1. Manual install Windows 8.1 Ent x64 on this laptop, and the all drivers one by one. I download the drivers from here: http://en.community.dell.com/techcenter/enterprise-client/w/wiki/7595.latitude-e54505450-windows-8-1-driver-pack 2. All the drivers installed great, as well as the network driver. Just to be sure I use a little free application called "DrvBK_21_Rev6" and back-up all the drivers. Of couse you can back-up the Network driver only. 3. From the SCCM console I import the driver I backup earlier and in the same time I verify the log "DriverCatalog.log" for any information. To my surprise I see this error: "Driver is not applicable to any supported platforms. Code 0x80070661". 4. Quickly searching the web I found this site: https://support.microsoft.com/en-us/kb/3025419 If you read carefully, there are 2 different KBs, one for Windows 8 and another one for Windows 7. I follow the one for Windows 8 "You cannot import a Windows 8 signed driver on a Windows Server 2008 R2-based WDS server" - https://support.microsoft.com/en-us/kb/2837108 5. Install the KB, restart the SCCM server. 6. After the restart, retry step #3, again during driver import check the log "DriverCatalog.log" for any information. This time everything went great and I see the message "Successfully initialized driver digest". 7. Go to \Software Library\Overview\Operating Systems\Boot Images, select the proper boot image, in my case its called ZeroTouch WinPE 6.3 x64, right click, select properties and go to Drivers. From here choose the little sun button and select the network driver I import earlier. Then Update Distribution Points. 8. Retry the Task Sequence installation, quickly hit F8 during pre installation boot and check for network connectivity. It works ! 9. Happy deploying. :-)
  7. Works like a charm ! In my case it wasn't necessary to restart the management point service. Thank you for your solution.
  8. Hello, Okay I finally figure it out, SCOM and SCSM can't share the default instance ! All I have to do was to create another named instance in SQL 2008 R2, after that follow the steps from here: http://technet.microsoft.com/en-us/library/ff461215.aspx and continue with the SCSM DW installation wizard, choose the new named instance instead of the default instance, it works ! I hope it helps the others too. Regards.
  9. Hello everyone, On my environment, I`m using a Windows Hyper-V Server 2008 SP1 with the following virtual machines: - Domain Controller ( AD,DNS,DHCP,CA) - Exchange 2010 SP1 - SCCM 2007 R2 SP2 - SCOM 2007 R2 ( SQL Server 2008 R2 Enterprise Ed. is also install on SCOM ) - SCSM 2010 SP1 I`m using Windows Server 2008 R2 SP1 for all virtual machines, and SQL Server 2008 R2. As you already noticed, I`m trying to integrate all of them as you successfully did in your tutorials, but I have an issue with SCSM – Data Warehouse installation Note: For the installation of all my servers in my environment I`m using Administrator as domain admin. On the SCOM server I also have the SQL Server 2008 R2, as default instance ( I`m not using any named instances ) When I install SCCM 2007 aka ConfigMgr Server, I use a SPN for installing the server ( http://technet.microsoft.com/en-us/library/bb735885.aspx ) Everything works great with that ! Now.. Just to be clear, for SCSM I’m using the 2 servers scenario ( http://technet.microsoft.com/en-us/library/ff460945.aspx ) I`m also using separate service accounts for every component: _svcSCSMService ( which is also a local administrator on both SCSM servers ) _svcSCSMWorkflow ( domain user ) _svcSCSMReporting ( domain user ) SCSMAdmins ( security group which includes the Administrator account as domain account ) On the first SCSM server, I install "Service Manager management server" component, everything went very well. Now, on the second SCSM server, I continue installing " Service Manager data warehouse management server" and every time I receive the following error: Configuring reporting - An error occurred while executing a custom action:_AssignDwAdminAsSsrsContentManagerOnRootFolder.1CA03A32_06E0 So from what I understand: _AssignDwAdminAsSsrsContentManagerOnRootFolder.1CA03A32_06E0_4726_8E63_FEA4484D9D6F = Sets the reporting account as the Content Manager on the System Center folder in SQL Server Reporting Services. I also found this: http://technet.microsoft.com/en-us/library/ff461019.aspx You will need the following permissions when installing the data warehouse management server: • Local administrator on the computer that you run Setup on • Local administrator on the computer that will host the data warehouse database if on a remote computer • Logged-in user must be a domain account • Content Manager role in SQL Server Reporting Services at the site level (root) • Sysadmin SQL Server role on the SQL Server instance where the data warehouse database is being created I don`t understand how to set content manager role in SQL SRS, I set SCSMAdmin as sysadmin as a new login in SQL, but when I tried to add SCSMAdmins group to my sql reports page - Site Settings – Security – New Role Assignment (http://msdn.microsoft.com/en-us/library/ms156034.aspx ) I receive this error : This is my users lists in AD: This is my SQL services accounts ( all are domain users ) This is my SQL Login list: SCSMAdmin account in SQL is sysadmin. Here are the Logs Does anyone have any idea or a hint on how to solve this issue ? Thank you, Best Regards, Bogdan.
  10. or here: http://blogs.technet.com/b/servicemanager/archive/2010/01/13/system-center-service-manager-demos.aspx Cheers.
  11. Hello, I think I found the solution, it was simple enough, actually it was in front of me all this time. You just have to follow this link, and read it carefully: How to Configure an SPN for SQL Server Site Database Servers Once the SPN is created all you have to do is to open SQL Server Configuration Manager and change SQL Server service account with the new SPN Still, I`m not sure if I have to change the other SQL services as well ( FullText Search, Browser and Agent ) ? Greetings.
  12. Hello anyweb, Fair question, but in my case, I have a separate SQL server, and I kinda forced to install SCCM 2007 this way. By remote I mean SQL is installed on another machine. I have to agree with you 100 % plus the Best practice for ConfigMgr is you have SQL locally ( http://technet.microsoft.com/en-ca/library/bb735870.aspx ) Of course, I know it would be much easier with both SQL and SCCM installed on the same server, but this isn`t possible for now, for licensing reasons only so it`s not really up to me to call the shots unfortunately. Thank you.
  13. Hello everybody, this is my first post on this great forum. I`m trying to install SCCM 2007 SP2 with SQL 2008 remote ( btw all my machines are vhd`s, I`m using Hyper-V ) My infrastructure looks like this: 1 SQL Server Std. 2008 SP2 x64 – Windows Server 2008 x64 1 Domain Controller - Windows Server 2008 SP2 x64 1 SCCM 2007 SP2 - Windows Server 2008 SP2 x64 Each machine is installed separately. Firewall is OFF, I have all prerequisites installed for the SCCM 2007 server, WSUS 3.0 SP2 is installed on the same server with SCCM. I add the SCCM computer account to the local admins on the SQL server When I try to install SCCM 2007, I receive this error: If I check my prerequisites or I try to install SCCM 2007, I also get this error on the SQL Logs: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors.. [CLIENT: 192.168.1.5] Error: 18456, Severity:14, State:11 I`ve tried to follow this link right here, but still no luck : http://blogs.technet.com/b/configurationmgr/archive/2010/10/26/troubleshooting-duplicate-or-missing-spns-for-a-configmgr-2007-sql-database.aspx I also add an SQL login: NT AUTHORITY\Authenticated Users , but that doesn`t help either Adding NT AUTHORITY\ANONYMOUS LOGON as SQL login, solved the problem with installing SCCM, but when I erase it, the SCCM console failed: I suspect the SPN (service principal name) is not set as it should, but I`m not sure this is the main problem. Maybe someone else could kindly help me solving this issue. Thank you, Greetings.
×
×
  • Create New...