Hi!

I got some problem when I tried to install Windows Server Update Services on my Test Windows Server 2012 Sp1 with SQL Server 2012 Sp1 installed. The Role installation worked fine. When after a post-installation runs it fails. After some research, I notice the post-installation didn’t found the wsusutil.exe tool (Wsus post-installation use this tool to do a post-installation). I’d a simple file search on server, and found the tool under c:\Program Files\Update Services\Tools. Run it from a powershell console:

 If you have install Wsus and choosed Database, run this command:

wsusutil.exe postinstall CONTENT_DIR="WSUS-CONTENT-PATH" SQL_INSTANCE_NAME="SQL-SERVER-NAME"


Skärmavbild 2013-09-04 kl. 11.20.08

If you have install Wsus and choosed WID database, run this command:

wsusutil.exe postinstall CONTENT_DIR=C:\WSUS INSTANCE_NAME="computername\database_instance_name"

During SQL 2012 SP1 installation on a Windows 2012 Server i got the following Error.

sql_error

The installation finished with some error.

sql_error2

To fix this, first I need to install .Net Framwork 3.5 and then mount my windows 2012 media as D:\ and run the follwoing command as administrator.

Dism /online /enable-feature /featurename:NetFx3 /All /Source:D:\sources\sxs

sql_error3

I rerun the SQL setup and successfully installed it.

sql_error4

During the installation of the new System Center Configuration Manager 2012 with Microsoft SQL Server 2012 I got the following error and the installtion couldn´t continue.

ERROR: Failed to get SID for user (NT Service\MSSQLSERVER)
ERROR: Failed to get the buffer size for LookupAccountName. Error= 1722

 

To fix it: I creat a domain account that has administrative right on the server and change the service account that the SQL services are running with to it and ran the setup again. This time it finished with no errors.

Mastering System Center 2012 Configuration Manager (SCCM)

The latest version of System Center Configuration Manager (SCCM) is a dramatic update of its predecessor Configuration Manager 2007, and this book offers intermediate-to-advanced coverage of how the new SCCM boasts a simplified hierarchy, role-based security, a new console, flexible application deployment, and mobile management. You’ll explore planning and installation, migrating from SCCM 2007, deploying software and operating systems, security, monitoring and troubleshooting, and automating and customizing SCCM 2012 with scripts.

http://www.bokus.com/bok/9781118128985/mastering-system-center-2012-configuration-manager-sccm/

Have gotten the Task Sequence error code 0x80072F87 lately and you have no clue of what it means or why your task sequences won’t run even though everything looks OK?

Well this little bugger kept me and the whole team where I am assigned at confused for a day or two.

The solution was simple: The computer date and time was wrong.

So fix the date and time and you’re all set to go.

Good Luck! 🙂

System Center 2012 Configuration Manager


Microsoft has made Release Candidates available for several of the upcoming 2012-editions of their System Center products.

Most interesting for us deployment guys is of course the release candidate of
System Center 2012 Configuration Manager.

As you all know, SCCM provides comprehensive configuration management for the Microsoft platform that can help you empower users with the devices and applications they need to be productive while maintaining corporate compliance and control.

DOWNLOAD

New and improved capabilities in the RC include:

  • Improved endpoint protection functionality, with integrated setup, management and reporting for System Center 2012 Endpoint Protection.
  • Improved application catalog design that provides a better, more responsive experience when requesting and downloading applications.
  • New support for Windows Embedded devices, including Windows Embedded 7 SP1, POSReady 7, Windows 7 Think PC, and Windows Embedded Compact 7.
  • Improved client status checks for Configuration Manager services and features.
  • Improved compliance enforcement and tracking, with the ability to create dynamic collections of baseline compliance and the generation of hourly compliance summaries.
  • Platform support for deep mobile device management of Nokia Symbian Belle devices. Pending a platform update by Nokia later this calendar year for these devices, customers will be able to try out the management of these Nokia devices with ConfigMgr.
  • Additional scalability and performance improvements.

Check out Technet for a more detailed description of What’s New in Configuration Manager 2012

Read more about and get all the Microsoft System Center 2012 Pre-Release Products here: http://technet.microsoft.com/sv-se/evalcenter/hh505660.aspx

Also, don’t forget to try out the Microsoft Deployment Toolkit 2012 Beta 1:
http://go.microsoft.com/fwlink/?LinkId=217606

 

Många organisationer har ett behov av att kunna PXE-boota datorer som redan finns med i SCCM-databasen det vill säga när en dator redan finns med i SCCM så går det inte att PXE-boota den då den inte längre är ”unknown”.

Det kan du lösa på följande sätt:

1. Det första man måste göra är att skapa en regfil som man döper till ”Imageversion.reg” där innehållet bör se ut som nedan:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ImageVersion]
"DisplayVersion"="1.0"
"Publisher"="Consulta Deployment Services AB"
"EstimatedSize"=dword:00000001
"DisplayName"="Image Version Win 7"

Denna regfil lägger till info om att OS-versionen är Win 7 samt att imageversionen är 1.0

2. Skapa ett SCCM-paket av filen Imageversion.reg som du döper till Image Version.

3. Lägg sedan in en task i TS (i samband med att alla andra appar installeras) som installerar/kör paketet Image Version som du skapade under punkt 2

4. När en dator sedan installeras via SCCM så läggs nyckeln  in via tasksequencen och där information om vilken image version som datorn är installerad med. Denna ”stämpel” kan man även använda framöver för att identifiera vilka versioner av images man har ute i miljön.

5. Skapa sedan en collection som du döper till något passande ex: Known Computers och lägg till följande collection-query:

SELECT
   SMS_R_SYSTEM.ResourceID
   ,SMS_R_SYSTEM.ResourceType
   ,SMS_R_SYSTEM.Name
   ,SMS_R_SYSTEM.SMSUniqueIdentifier
   ,SMS_R_SYSTEM.ResourceDomainORWorkgroup
   ,SMS_R_SYSTEM.Client
FROM
   SMS_R_System INNER JOIN SMS_G_System_ADD_REMOVE_PROGRAMS ON
      SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceId = SMS_R_System.ResourceId
WHERE
   SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = "Image Version Win 7"

 

6. När SCCM sedan kommunicerat första gången med den nyinstallerade datorn så kommer datorn via en collection-query att hamna I den collection som du skapade under föregående punkt, och att du kommer kunna PXE-boota igen, se till att din TS är publicerad till denna collection men att den INTE är mandatory.