System Center Update Publisher 2011 on Windows Server 2012

SCUP 2011 is not compatible with Windows Server 2012 but there is a workaround to work, except for the following known issues:

  1. On Windows Server 2012, the WSUS version is 4.0. While on all other OS’s, you can only install WSUS 3.0 (with or without service pack). WSUS 3.0 & WSUS 4.0 cannot communicate with each other. So if you install SCUP on a machine with WSUS 3.0 admin console and try to publish to Windows Server 2012 with WSUS 4.0, you’ll get a WSUS version mismatch error in the SCUP log.
      • You can, however, install SCUP 2011 on Windows 8 and publish to the WSUS on Windows Server 2012. You need to install Remote Server Administration Tools for Win 8 http://www.microsoft.com/en-us/download/details.aspx?id=28972 on Windows 8 machine. It will install the WSUS 4.0 version of the WSUS admin console binary on Win 8. And with that, you can talk with WSUS 4.0 on Windows Server 2012.

2.  Low right user scenario is broken currently on Windows Server 2012. Normally, the user should only be in the WSUS administrative group to publish updates successfully. But the user to use and publish update to Windows Server 2012 must be a member of the local administrator.

Workaround for this: (do the followings changes, on the Windows Server 2012, at your own risk)

  1. Change the ownership of HKEY_CLASSES_ROOT\AppID\{8F5D3447-9CCE-455C-BAEF-55D42420143B} to Administrators – Change the permission on that key. Make sure Administrators and System have full control on that (http://technet.microsoft.com/en-us/library/cc786173(v=WS.10).aspx)
  2. Launch Dcomcnfg.exe in elevated mode.
  3. Select “Component Services – “Computers – “My Computer– “Dcom Config” – “WSusCertServer”, and press Right Click and select “Properties“.
  4. WSusCertServer Properties” dialog will show up, and click on “Security tab
  5. Set “Launch and Activation Permissions” and “Access Permissions” like the following

   

6.  Restart WSusCertServer service (net stop/net start)

Hope you enjoy using SCUP 2011 with Windows Server 2012.

Article has been copied from: http://blogs.msdn.com/b/minfangl/archive/2012/12/01/system-center-update-publisher-2011-and-windows-server-2012.aspx

Udgivet i SCCM, SCCM 2012 R2, SCUP, SCUP 2011, Windows 8, Windows Server 2012, WSUS | Skriv en kommentar

How to convert VMware-based virtual machines and disks (VMDK) to Hyper-V®-based virtual machines and disks (VHD), using Microsoft Virtual Machine Converter Solution Accelerator (MVMC)

The Microsoft Virtual Machine Converter (MVMC) Solution Accelerator is a Microsoft-supported, stand-alone solution for the IT pro or solution provider who wants to convert VMware-based virtual machines and disks to Hyper-V®-based virtual machines and disks.

The conversion of VMware virtual machines to Hyper-V consist in 3 Steps:

  1. Install the Microsoft Virtual Machine Converter Solution Accelerator
  2. Convert the VMWare disk to Hyper-V disk format, using the MVDC.exe tool
  3. Create a new Virtual Machine on Hyper-V using the disk that was convert

Install the Microsoft Virtual Machine Converter Solution Accelerator

  • Download the Microsoft Virtual Machine Converter Solution Accelerator.msi software from Microsoft here
  • Run the Microsoft Virtual Machine Converter Solution Accelerator.msi and Click Next

  • Accept the terms and Click Next

  • Click Next

  • Click Install

  • Click Finish

Convert the VMWare disk to Hyper-V disk format, using the MVDC.exe tool

To convert the VMWare disk, open a Command Prompt (cmd) as Administrator

  • On the cmd, write cd %programfiles(x86)%\Microsoft Virtual Machine Converter Solution Accelerator


  • Use the following parameter to convert a VMDK file to a VHD file: MVDC.exe “locationofthefile\Test.vmdk” “locationofthefile\Test.vhd” to start converting


  • Conversion is finish

Create a new Virtual Machine on Hyper-V using the disk that was convert

  • Right Click on the Hyper-V server and select New – Virtual Machine…

  • Click Next

  • Choose the name and Click Next (You can also choose to Store the VM in a different location)

  • Select Generation 1 and Click Next

  • Specify the amount of memory to allocate to the Virtual Machine and Click Next

  • Configure the Network Adapter and Click Next (You can change this configuration after the creation of the VM)

  • Select Use an existing virtual hard disk, Click on Browse, locate and select the disk you had convert and Click Next

  • Click on the Start button , to start the Virtual machine

Voilà le Virtual Machine is now working on Hyper-V

Udgivet i General, Guides, Virtual Machine | Skriv en kommentar

Disable UAC for some applications in Windows 7

To disable UAC of some application in Windows 7, you just follow the instruction below

 

  1. Download and install Microsoft Application Compatibility Toolkit 5.6
  2. Open the Compatibility Administrator, Right click it and click Run as administrator

  1. Right-click on the database, under Custom Databases, and select Create New, and select Application Fix

  1. Enter the name of the program, vendor and select the program file location and Click Next

  1. On Compatibility Mode, Click Next
  2. On the Compatibility Fixes, check it RunAsInvoker, and Click Next

  1. Click Finish
  2. Click Save the file as NameOfTheApp.sdb

To apply the Compatibility Database Fix just follow the next steps:

  1. Run the Windows Command Process (cmd) as administrator
  2. To install the database compatibility fix, run this command sdbinst –q NameOfTheApp.sdb (Run the command from the location where the database is saved)


Now you can open your application without the UAC popup all the time

Note: To uninstall the
database compatibility fix, run this command sdbinst –u NameOfTheApp.sdb

Udgivet i Uncategorized | Skriv en kommentar

Microsoft System Center 2012 Service Pack 1 Configuration Manager – Clients for Additional Operating Systems

The Clients for Additional Operating Systems allow you to manage Apple Mac, UNIX and Linux computers using System Center 2012 Configuration Manager SP1

Download and more details: http://www.microsoft.com/en-us/download/details.aspx?id=36212

Overview

Microsoft System Center 2012 Configuration Manager SP1 supports the management of Apple Mac clients. The client for Mac computers allows you to discover, collect inventory, manage settings, and deploy applications and patches using your Configuration Manager environment.

Microsoft System Center 2012 Configuration Manager SP1 also supports the management of UNIX and Linux servers. The clients for UNIX and Linux extends the scope of your Configuration Manager environment to collect inventory, deploy software, and run reports about UNIX and Linux servers in your enterprise. The client operates as a workgroup client that is managed by Configuration Manager.

Mac Client:
The following Mac versions are supported in this release:

  • Mac OS X 10.6 (Snow Leopard)
  • Mac OS X 10.7 (Lion)
  • Mac OS X 10.8 (Mountain Lion)

The following scenarios are supported through the Mac client in Microsoft System Center 2012 Configuration Manager SP1: 

  • Discovery – Discovers Mac OS X system in Active Directory and through network discovery
  • Hardware Inventory – Provides hardware inventory and auditing of computers running Mac OS X, including a list of installed software similar to add/remove programs for Windows systems.
  • Settings Management – Ensures computers running Mac OS X comply with company policies using scripts and preference list management.
  • Application Deployment – Distributes required software via app model.
  • Software Updates Management – Distributes patches utilizing Software Distribution and Settings management features.

UNIX/Linux Client:
The following UNIX and Linux versions are supported in this release. 

  • RHEL Version 6 (x86 & x64)
  • RHEL Version 5 (x86 & x64)
  • RHEL Version 4 (x86 & x64)
  • Solaris Version 10 (x86 & SPARC)
  • Solaris Version 9 (SPARC)
  • SLES Version 11 (x86 & x64)
  • SLES Version 10 SP1 (x86 & x64)
  • SLES Version 9 (x86)

The following scenarios are supported by the UNIX and Linux clients: 

  • Hardware Inventory – Hardware inventory can be viewed through Resource Explorer and can be used to create collections of UNIX and Linux computers.
  • Software Inventory – Through hardware inventory the list of natively installed software can be gathered from the UNIX and Linux computers – similar to add/remove programs for Windows systems.
  • Software Distribution – Deploy new software, update existing software and apply OS patches to collections of UNIX/Linux computers (using a package and program). Run arbitrary maintenance scripts on a collection of UNIX/Linux servers.
  • Secure and Authenticated Communications
  • Consolidated Reports

Release History:
Mac Client:
1/3/2013: Client Build Version 5.00.7804.1000 

  • System Center 2012 SP1 RTM version
  • Applicable to Mac OS X 10.6 & Mac OS X 10.7

4/1/2013: Client Build Version 5.00.7804.1202 

  • System Center 2012 SP1 CU1 version
  • Applicable to Mac OS X 10.6, 10.7 & 10.8

UNIX/Linux Client:
1/3/2013: Client Build Version* 1.0.0.4008

  • System Center 2012 SP1 RTM version
  • Applicable to all supported versions of RHEL, SLES and Solaris

2/4/2013: Client Build Version* 1.0.0.4014 

  • Includes fix for File Inventory policy processing
  • Applicable to all supported versions of RHEL, SLES and Solaris

Note: The UNIX/Linux Client Build Version can be determined from the filename of the client package tar file. For example in the case of the filename ccm-RHEL6x86.1.0.0.4014.tar, the Client Build Version is 1.0.0.4014.

System requirements

Supported operating systems: Linux, Mac OS X, Unix

Supported configurations and hardware requirements for Mac: See the Client Requirements for Mac computers section in the Supported Configurations for Configuration Manager topic. http://technet.microsoft.com/en-us/library/gg682077.aspx

Supported configurations and hardware requirements for UNIX/Linux: See the Client Requirements for Linux and UNIX Servers section in the Supported Configurations for Configuration Manager topic. http://technet.microsoft.com/en-us/library/gg682077.aspx 

Supported versions of Configuration Manager: System Center 2012 Configuration Manager SP1

Instructions

Mac Client:

  1. Download the Mac client msi file to a Windows system
  2. Run the msi and it will create a dmg file under the default location “C:\Program Files (x86)\Microsoft\System Center 2012 Configuration Manager Mac Client” on the Windows system
  3. Copy the dmg file to a network share or a folder on a Mac computer
  4. Access and open the dmg file on a Mac computer and install the client using instructions in the online documentation.http://technet.microsoft.com/en-us/library/jj591553.aspx

Unix/Linux Clients:

  1. Download the appropriate file for the UNIX/Linux operating system you wish to manage to a Windows computer
  2. The downloaded file is a self-extracting exe and will extract tar files for the different versions of your operating system.
  3. Copy the install script and the .tar file for your computer’s operating system version to a folder on your UNIX/Linux computer.
  4. Install the client using instructions in the online documentation. http://technet.microsoft.com/en-us/library/jj573939.aspx
Udgivet i Uncategorized | 2 kommentarer

Check the client version after updating the SCCM 2012 SP1 with CU1

After the installation of the CU1, for ConfigMgr 2012 SP1, the client will update to version 5.00.7804.1202.

To control the clients that are now updated or not, you can create a two queries to control the version of the clients.

The following query show you the list of clients (Computers) that have the upgraded client:

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_SMS_ADVANCED_CLIENT_STATE on SMS_G_System_SMS_ADVANCED_CLIENT_STATE.ResourceId = SMS_R_System.ResourceId where SMS_G_System_SMS_ADVANCED_CLIENT_STATE.Version = “5.00.7804.1202″

 

The following query show you the list of clients (Computers) that still don’t have upgrade the client:

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_SMS_ADVANCED_CLIENT_STATE on SMS_G_System_SMS_ADVANCED_CLIENT_STATE.ResourceId = SMS_R_System.ResourceId where SMS_G_System_SMS_ADVANCED_CLIENT_STATE.Version < “5.00.7804.1202″

Udgivet i Uncategorized | Skriv en kommentar

KB: Windows 8 fix for Cisco VPN Client & Cisco AnyConnect

Cisco VPN Client fix for Windows 8

Problem case:

While trying to connect to a VPN you meet the following error message:

“Secure VPN Connection terminated locally by the Client”

“Reason 442: failed to enable Virtual Adapter”

Læs resten

Udgivet i KB | Skriv en kommentar

Error upgrading Secondary Site after SCCM 2012 upgrade to SP1

[Failed]: Configuration Manager primary site and central administration site require SQL Server Tcp is enabled and set to Static port.

Just open the SQL Server Configuration Manager in the Primary/Central Site and in the Secondary Site and remove all the Dynamic Ports (If the TCP Dynamic Ports option is configure with 0, the Dynamic port is active)

  1. Open SQL Server Configuration Manager with administrator right and remove all 0 from option TCP Dynamic Ports;

     

    Should be like this example:

     

  2. After disable the TCP Dynamic Ports in both servers and in all IP protocols, run again the Secondary Site Upgrade, and check the logs.

More Info:

How to configure SQL Server to listen on a specific port: http://support.microsoft.com/kb/823938

Udgivet i Uncategorized | Skriv en kommentar