NEWS ANALYSIS: Sprint's board has a tough choice when it comes to picking the buyout suitor that offers the best deal for investors and the company's long-term growth.
By Steve Schmidt DevOps has become an increasingly hot topic. It was covered in the Microsoft Management Summit (MMS) 2013 keynote as well as in a variety of sessions at that event, and has been in the news with […]
MS KB 2817245 (CU1 for SP1) Applies to Microsoft System Center 2012 Configuration Manager (SP1) 2780664 (CU2) Applies to Microsoft System Center 2012 Configuration Manager 2717295 (CU1) Applies to Microsoft […]
REVIEW: IP Address Manager from SolarWinds brings centralized monitoring and management to complex IP infrastructures and provides administrators with advanced troubleshooting tools.
Originally released on 2011, the Service Manager connector for Exchange has been updated to version 3.0. This version fixes several bugs and improves the functionality. The Exchange connector helps automate […]
Microsoft vient d'annoncer la disponibilité du Cumulative Update 1 pour SCCM 2012 SP1. Il est disponible au téléchargement à l'adresse suivante : http://support.microsoft.com/kb/2817245/fr
Corrections :
Administrator Console
A Discovery Data Record (DDR) that contains organizational unit (OU) paths that are longer than 220 characters are not processed. The DDM.log file on the site server contains event messages that resemble the following:
CDiscoverySource::ValidateSchema – array property User OU Name cannot expand size so rejecting.
CDiscoverDataManager::ProcessDDRs – Unable to update data source
The Allow clients to use a fallback source location for content option is missing from the Distribution Points tab of the package properties.
Site systems
Replication Configuration Manager incorrectly reports the link status as Degraded and then reports the status as Active one minute later.
Site replication fails after a site database is restored to a new server. Additionally, the Rcmctrl.log file contains the following error message:
ERROR: Received unhandled SQL exception, printing info and throwing it again. This will be retried in next cycle. SqlException number: [8115] ERROR: Exception message: [Arithmetic overflow error converting expression to data type int.~~The 'spGetChangeTrackingMinValidVersion' procedure attempted to return a status of NULL, which is not allowed. A status of 0 will be returned instead.]
Device management
The Configuration Manager client cannot be installed on devices that contain newer ARM processors. Additionally, the following error message is logged in the DmClientSetup log file:
Fail to get the CAB file name because of unsupported processor type: 0
Software updates
The Allow clients to share content with other clients on the same subnet option in the properties of a Software Update Group Deployment is ignored. Additionally, the DataTransferService.log file contains the following message:
Not using branch cache option.
When a custom port is configured for software updates, an Internet only client may append the custom port to the URL for the Windows Update service. Additionally, when the custom port is set to 880, log entries that resemble the following may be logged in the DataTransferService.log file:
The Schedule Updates Wizard does not list content for Windows Server 2012. For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:
2793237 FIX: The Schedule Updates Wizard does not list content for Windows Server 2012 in System Center 2012 Configuration Manager Service Pack 1
Client
The MicrosoftPolicyPlatformSetup.msi file is now correctly signed.
The selection of multiple targeted applications in Software Center will fail if the calendar region is set to Arabic (Saudi Arabia). Additionally, Software Center displays the following error message:
Software Center cannot be loaded. There is a problem loading the required components for Software Center. You can try launching Software Center at a later time. If the problem continues, you can contact your helpdesk.
The hardware inventory on a computer that is running a 32-bit version of Windows Server 2003 R2 may cause the Wmiprvse.exe process to exit unexpectedly. Additionally, when you view the results of the fault, the details of the fault resemble the following:
Faulting application wmiprvse.exe, version 5.2.3790.4455, faulting module msvcr90.dll, version 9.0.30729.6161, fault address 0x00056b1d
PXE support is added for IA-32 EFI computers.
PowerShell
When the Clear-CMPxeDeployment cmdlet is run, you receive the following error message:
The method or operation is not implemented.
When the Update-CMDistributionPoint –DeploymentTypeName cmdlet is run, you receive the following error message:
Key not Found Exception.
When the New-CMDeviceCollection cmdlet is run, the refreshschedule parameter is not defined in the NewByLimitName parameter set.
When the New-CMDeviceCollection cmdlet is run together with the LimitingCollectionName option, the cmdlet is unsuccessful. Additionally, you receive the following error message:
Unable to cast object of type 'Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlArrayItems' to type'System.Management.ManagementBaseObject'.
When the .GetType method is used for the object that is returned by the New-CMSchedule cmdlet, the method is unsuccessful. Additionally, you receive the following error message:
The adapter cannot get property "GetType" for instance of SMS_ST_RecurInterval.
When the Import-CMComputerInformation -CollectionName "All Systems" -ComputerName "Computer01" -MacAddress "xx:xx:xx:xx:xx:xx" command is run, the command is unsuccessful. Additionally, you receive the following error message:
WARNING: The collection All Systems does not exist or is not suitable for adding the new device.
Nouvelles fonctionnalités :
PowerShell
Help for PowerShell is updated for the cmdlets that are included in Configuration Manager Service Pack 1 and in this cumulative update. In a PowerShell environment, use the Update-Help –Module ConfigurationManager cmdlet to retrieve the latest Help information from Microsoft.
The following cmdlets are added to the PowerShell module:
É comum nos depararmos com algumas situações em que precisamos saber qual a versão do nosso SCCM pela Build. Para isso criei uma tabela com as versões.
Produto
Revisão
Lançamento
Service Pack
Versão/Build
Systems Management Server (SMS)
1.0
1994
Systems Management Server (SMS)
1.1
1995
Systems Management Server (SMS)
1.2
1996
Systems Management Server (SMS)
2.0
1999
Systems Management Server (SMS)
2003
2003
Systems Management Server (SMS)
2003 R2
2006
System Center Configuration Manager (ConfigMgr)
2007
2007
Beta 1
4.00.5135.0000
System Center Configuration Manager (ConfigMgr)
2007
2007
RTM
4.00.5931.0000
System Center Configuration Manager (ConfigMgr)
2007
2008
SP1
4.00.6221.1000
System Center Configuration Manager (ConfigMgr)
2007
2009
SP2
4.00.6487.2000
System Center Configuration Manager (ConfigMgr)
2007
2010
SP2
4.00.6487.2111
System Center Configuration Manager (ConfigMgr)
2007
2010
SP2 R3
4.00.6487.2157
System Center 2012 Configuration Manager (ConfigMgr)
2012
2010
Beta 1
System Center 2012 Configuration Manager (ConfigMgr)
2012
2011
Beta 2
5.00.7561.0000
System Center 2012 Configuration Manager (ConfigMgr)
2012
2011
RC 1
5.00.7678.0000
System Center 2012 Configuration Manager (ConfigMgr)
2012
2012
RC 2
5.00.7703.0000
System Center 2012 Configuration Manager (ConfigMgr)
2012
2012
RTM
5.00.7711.0000
System Center 2012 Configuration Manager (ConfigMgr)
2012
2012
CU 1
5.00.7711.0200
System Center 2012 Configuration Manager (ConfigMgr)
2012
2012
CU 2
5.00.7711.0301
System Center 2012 Configuration Manager (ConfigMgr)
2012
2012
SP1 Beta
5.00.7782.1000
System Center 2012 Configuration Manager (ConfigMgr)
EGS is now selling Adaptiva deliverables in the Metro NY/Northeast Region. Some of Adaptiva's customers include Barclays, HSBC, Walmart, etc.
Adaptiva Overview
Streamline IT operations, extend the functionality of Microsoft System Center ConfigMgr 2012 and rapidly improve ROI
Simply Works!
According to Gartner Executive Programs' 2012 CIO Agenda worldwide survey of 2,335 CIOs in the fourth quarter of 2011, CIO's top three strategies for 2012 focus on delivering business solutions, reducing the cost of IT and managing a flexible infrastructure.1 Gartner believes IT departments will continue to be challenged to deliver quality end-to-end services in a rapidly changing multi-source environment.
Founded in 2004 and a Microsoft Gold Partner, Adaptiva is a leader in systems management solutions. Adaptiva solutions leverage existing IT resources to enhance the operation of Microsoft System Center Configuration Manager 2012 without disrupting service to end-users. Adaptiva conquers the complexity of IT by streamlining operations, extending the functionality of Microsoft System Center Configuration Manager (SCCM) 2012 and rapidly improving ROI on existing systems. Adaptiva provides easy to use software that seamlessly integrates with Microsoft SCCM to help you better manage your IT while reducing the total cost of ownership.
Adaptiva Software Suite
OneSite. Provides the ability to run Microsoft SCCM 2012 from a single site, even in complex global networks, and eliminates SCCM server infrastructure, including all child primary sites, secondary sites and distribution points. OneSite delivers any content to any PC anytime, anywhere and rapidly improves ROI.
Green Planet. Offers a collaborative approach to PC power management with no end-user impact. Green Planet automatically wakes PCs to perform systems management tasks such as patching, and dramatically reduces energy consumption, minimizing environmental impact and saving money.
Client Health. Automatically diagnoses and remediates malfunctioning PCs and performs WMI self-diagnosis and auto-repair. A sophisticated workflow designer and orchestration engine allows administrators to design custom health checks and remediations, without having to write code. Fully integrated with SCCM 2012. The recipient of awards and accolades, Adaptiva software is deployed on more than 2 million devices globally and sold directly and through a network of partners and channel resellers in more than 14 countries. Adaptiva is privately held and based in Bellevue, Washington. Get Started Today! Learn how Adaptiva can enhance your IT processes while reducing your total cost of ownership. Mitch Morrison
Typically System Center 2012 SP1 components receive Update Rollups together at the same time but it seems ConfigMgr is still exception to that. Cumulative Update 1 for System Center 2012 Configuration Manager SP1 is released by MSFT. This update contains several fixes and believe it or not new functionalities in the form of new PowerShell cmdlets:
Add-CMDistributionPoint
Import-CMAntiMalwarePolicy
Import-CMDriver
New-CMAppVVirtualEnvironment
New-CMMigrationJob
New-CMPackage
New-CMSoftwareUpdateAutoDeploymentRule
New-CMTaskSequence
New-CMTaskSequenceInstallUpdateAction
New-CMTaskSequenceMedia
New-CMUserDataAndProfileConfigurationItem
Remove-CMTaskSequenceInstallUpdateAction
Set-CMTaskSequenceGroup
New-CMTaskSequenceGroup
Remove-CMTaskSequenceGroup
Set-CMApplicationCatalogWebsitePoint
Set-CMAppVVirtualEnvironment
Set-CMClientPushInstallation
Set-CMClientSetting
Set-CMDistributionPoint
Set-CMDriver
Set-CMEndpointProtectionPoint
Set-CMEnrollmentPoint
Set-CMEnrollmentProxyPoint
Set-CMHierarchySetting
Set-CMManagementPointComponent
Set-CMOperatingSystemImageUpdateSchedule
Set-CMOutOfBandManagementComponent
Set-CMReportingServicePoint
Set-CMSite
Set-CMSoftwareUpdateAutoDeploymentRule
Set-CMSoftwareUpdatePointComponent
Set-CMStateMigrationPoint
Set-CMStatusSummarizer
Set-CMSystemHealthValidatorPointComponent
Set-CMTaskSequence
Set-CMTaskSequenceInstallUpdateAction
Set-CMUserDataAndProfileConfigurationItem
Start-CMDistributionPointUpgrade
You can find out about the fixes and download CU1 from here.
I guess the name explain it all , employee in a company always complain that Helpdesk not answering the calls , slow response ..also some installation they need to send a tech support to employee office .
guess what with app portal software , employee will do it by her/him self .
the good thing also it has it is own workflow ,so still Helpdesk or admin to approve or deny , and it integrate with Microsoft SCCM .
this is the future , why to call Helpdesk of you can do it ur self .
now Self Service web or app spreading , and i beleive it is adding huge value .
ya last , SCCM 2012 has it own web for self service but microsoft didnt mention much .
Kerberos authentication uses an identifier called the "Service Principal Name" or SPN. Basically, the SPN acts as a domain or forest unique identifier of some instance in a server resource. There can be an SPN for a web service, for an SQL service, or for an SMTP service. There can also be multiple web service instances on the same physical computer that has a unique SPN.
This becomes abundantly clear at almost every client I install SCCM for. Most DBAs seem to stick with the well-established best practice of running the SQL services under seperate domain accounts. And most companies seem to want to grant service accounts the least privileges needed: another best practice indeed. As a result, the SPN can fail to be created for the SQL instance for ConfigMan:
Why does this happen? By default, if you run the SQL Server service under the LocalSystem account, the SPN is automatically registered and Kerberos authentication interacts successfully with the computer that is running SQL Server. However, if you run the SQL Server service under a domain account or under a local account, the attempt to create the SPN can often fail in most cases because the domain or local accounts do not have the rights to set their own SPNs. When the SPN creation is not successful, it can prevent you from using Kerberos authentication when connecting to the SQL server instance. If this were done with a domain administrator account as the SQL Server service account, the SPN would be successfully created because the domain administrator-level credentials that you must have to create an SPN are present.
Most people will opt not to use a domain administrator account to run the SQL Server service and therefore, you must manually create an SPN for your computer that is running SQL Server if you want to use Kerberos authentication when you connect to it. The SPN you create must be assigned to the service account of the SQL Server service on that particular computer. The SPN cannot be assigned to the computer container unless the computer that is running SQL Server starts with the local system account. There must be one and only one SPN, and it must be assigned to the appropriate container. Typically, this is the current SQL Server service account.
To configure the SQL Server service to create SPNs dynamically, follow these steps: 1. Click Start, click Run, type Adsiedit.msc, and then click OK.
2. In the ADSI Edit snap-in, expand Domain [DomainName], expand DC= RootDomainName, expand CN=Users, right-click CN= AccountName, and then click Properties.
3. In the CN= AccountName Properties dialog box, click the Security tab.
4. On the Security tab, click Advanced.
5. In the Advanced Security Settings dialog box, make sure that SELF is listed under Permission entries.If SELF is not listed, click Add, and then add SELF.
6. Under Permission entries, click SELF, and then click Edit.
7. In the Permission Entry dialog box, click the Properties tab.
8. On the Properties tab, click This object only in the Apply onto list, and then make sure that the check boxes for the following permissions are selected under Permissions: Read servicePrincipalName Write servicePrincipalName
9. Click OK three times, and then exit the ADSI Edit snap-in.
To Create an SPN from the command line:
1. Open a Command Prompt or PowerShell from and account with Domain Admin priveleges
2. Type setspn -A MSSQLSvc/server:instance domain\account
3. After the command completes, type setspn -Q MSSQLSvc/server:instance to verify the SPN is successfully created and present.
Insight Control for Microsoft System Center is a package of integration kits that aim to integrate HP Hardware and Software with Microsoft System Center. Here is the description of these integration kits taken from the HP site:
System Center Operations Manager (SCOM) support:
The HP ProLiant and BladeSystem Management Packs expose the native capabilities of ProLiant and BladeSystem servers and enclosures to help prevent problems from occurring by proactively monitoring and managing hardware health and intelligently responding to hardware events on servers running Windows.
The HP ProLiant Agentless Management Pack manages the health of ProLiant Gen8 servers without the need for loading OS-based SNMP agents or WBEM providers. It can also be used to monitor the health of servers that do not have an OS yet loaded, as well as ProLiant Gen8 servers running any operating system that has a supported Agentless Monitoring Service (such as VMware ESXi).
The HP ProLiant Linux and VMware Management Packs provide the ability to monitor hardware health and configuration, as well as to receive HP hardware alerts, on ProLiant servers running Linux and VMware ESX.
Supports SCOM 2007 and SCOM 2012 (including SP1) for all HP SCOM management packs.
System Center Virtual Machine Manager (SCVMM) support:
The HP Performance Resource Optimization (PRO) Management Pack reduces unplanned downtime by proactively automating live migration of Hyper-V virtual machines based upon HP pre-failure and predictive hardware alerts from ProLiant servers. Supports SCVMM 2008.
HP SCVMM 2012 Integration Kit provides HP WinPE and production drivers for ProLiant servers to assist with OS deployment via SCVMM 2012 (including SP1).
The HP ProLiant Updates Catalog can be used by SCVMM 2012 (including SP1) to provide simplified Windows driver and firmware updates via a rotating, automated workflow for Hyper-V clusters.
System Center Configuration Manager (SCCM) support:
The HP ProLiant Server Operating System Deployment (OSD) feature provides quick and reliable Windows deployment to bare metal HP servers, including pre-deployment hardware and BIOS configuration, and post-OS HP driver and agent installation.
The HP ProLiant Updates Catalog ensures consistency and maximizes uptime with simplified Windows driver and firmware updates using the HP Service Pack for ProLiant.
The HP ProLiant Hardware Inventory Tool provides detailed component level inventory of every managed HP Windows server.
Supports SCCM 2007 and SCCM 2012 (including SP1).
Let's look what has changed from 7.1 version:
Support for Microsoft System Center Operations Manager (SCOM) 2012 SP1
Management packs certified with SCOM 2012 SP1
Support for Windows Server 2012 monitoring
System Center Operations Manager (SCOM) Management Pack Updates
Updated system discovery rule for BladeSystem Management Pack
Updated WMI Provider for ProLiant DL980
Support for Microsoft System Center Configuration Manager (SCCM) 2012 SP1
Updated SCCM 2012 Integration Kit to support SCCM 2012 SP1 (supported only when SCCM 2012 SP1 is installed on Windows Server 2012)
Updated HP ProLiant Updates Catalog to support SCCM 2012 SP1
Support for Windows Server 2012 deployment and updates
Note: The HP SCCM 2012 Integration Kit is only supported on SCCM 2012 SP1 installed on Windows Server 2012
Note: OS deployments to Windows Server 2008 R2 Core are not supported
Support for Microsoft System Center Virtual Machine Manager (SCCM) 2012 SP1
Updated SCVMM 2012 Integration Kit to support SCVMM 2012 SP1
Updated HP ProLiant Updates Catalog to support SCVMM 2012 SP1
Support for Windows Server 2012 deployment and updates
Updates to support HP Service Pack for ProLiant (SPP)
New software bundles included in the HP ProLiant Updates Catalog to support Windows Server 2012
So we now have full SC 2012 SP1 and Windows Server 2012 support. This is great job of HP releasing support so soon after GA of SC 2012 SP1.
If you are wondering what have changed like versions on the SCOM management packs look here:
Keep in mind that new versions of the management pack for HP servers and blades will come only in this bundle Insight Control for Microsoft System Center. No separate downloads will be released. HP Storage Management Pack for now stays separate download and it is not provided in this package.
To download this new version go here. You only need to download Insight Control for System Center 7.2 DVD ISO – Mar 2013 for the System Center integration kits.
Ever get this message when PXE booting? I did again today. The PXE Server was running Windows Server 2008 R2 SP1, and PXE boot had been working perfectly until I applied some updates to the server last week. Following the server update, clients were unable to PXE boot, and the above error was displayed.
The fix? In my case I stumbled upon it in an online forum.
Open registry editor on the PXE server (regedit.exe)
The Sp1 Pre-Req check for SCCM 2012 is buggy I got different results each time I ran it. I finally manually checked everything then started the install. Migration of collections has started. Working with a few clients on both sites now.
Step
Results
Notes
Assess the current environment.
Current Environment looks good there are some items that I am removing
Review the functionality and changes that are available with the version of System Center 2012 Configuration Manager that you use, and use this information to help you design your destination hierarchy.
Will go into details on these post upgrade. Right now it is like for like
Determine the administrative security model to use for role-based administration.
There will be a full post on the Security model post uprade
Assess your network and Active Directory topology
Getting rid of seconday and replacing with DP
Finalize your destination hierarchy design.
Single Site server and a handfull of DPs. New Site code
Install a stand-alone primary if you do not plan to use a central administration site.
Map your hierarchy to the computers that you will use for sites and site servers in the destination hierarchy.
Server10 - SCCM 2012
Server11 – SCCM SQL Server
Server12 – New distribution Point
Server8 – Upgraded Distribution Point
Plan your object migration strategy.
completed
Plan your client migration strategy.
completed
Plan your client migration strategy.
completed
Plan for the completion of migration from the source hierarchy.
completed
Identify the computers to use in the destination hierarchy.
See Above
Create your destination hierarchy.
created server10,Server11 and Server 12
If you want to migrate information that is related to software updates, configure a software update point in the destination hierarchy and synchronize software updates.
skipping updates
Install and configure additional site system roles in the destination hierarchy.
added AppV
Verify operational functionality in the destination hierarchy.
all items work except reporting services. Will configure as migration is working
-All Pre Items ABOVE
Enable migration in the destination hierarchy.
Sites linked and Migrations of collections have started.
When the source hierarchy runs Configuration Manager 2007 SP2, select and configure additional sites in the source hierarchy.
Configure distribution point sharing.
Create and run migration jobs to migrate objects associated with the clients in the source hierarchy.
While troubleshooting some inactive SCCM clients I found that they had bad SMS Certs.
Symptoms of this were found in the locationServices.log
Failed to verify Certificate with error 0×80070057 was the error that pointed me to take a look at the SMS Cert.
Upon review I found that the certs were from a previous install of SCCM in my lab. These need to be deleted so the new install of SCCM can issue certs to the clients and establish a trust relationship.
My long term plan is to build a runbook to fix broken SCCM agents and this is a good place to start
Inside the scriptblock is the meat of the script, I delete the Certificates via the registry and then restart the SCCM agent service, the client will connect to the site server and request new certificates to be issued.
If this is the only problem on the machine it's status should become active in SCCM.
This script is provided as is and should not be used in a production environment against all computers in your domain.
Before you run the setup of Microsoft System Center Configuration Manager 2012 SP1, you must download and install Windows ADK on the site server and the provider computer.
I'm going to get this out the way first: Yes, I know SCCM 2012 has been out for a little while (and SP1 got launched too). Yes, I know it supports Windows 7 and 8 and has awesome new features for targeting applications at users.
But here's the rub, there's probably lots of companies with SCCM 2007 and XP who just want to get their company done and dusted with the Windows 7 upgrade, before they go and make life a bit more difficult by trying to do a SCCM upgrade, right in the middle of it.
I sure as hell do.
SCCM 2007 R3 was supposed to give us full support for Windows 7 and Windows 2008 R2 so that we can quickly migrate to Windows 7 and reap all the benefits of a new OS (Yes I know Windows 8 is out now, too).
So why in all that is holy was Fast User Switching not supported in SCCM 2007? Yes you heard me it isn't supported, in fact what you will get is that the second user who logs on to a Windows 7 computer won't see anything in "Run Advertised Programs" and no user targeted advertisements will run until the first person logs out. The split second that happens the SCCM client kicks in and RAP populates and all those wonderful app-v applications deploy.
You'll find the support statement on this page on the TechNet site. No hotfix or update is available as far as I can see (if anyone can correct me I will be indebted to you!) and that's just that. I'm partially placated by the fact that we'll do a SCCM 2012 upgrade and get this sorted, but when you consider all the hoopla about Windows 7 and all the Teched sessions about deploying it, how did this slip by? (I must have missed the Teched session where someone mentioned FSU, probably the day after Techfest ).
It seems to be a constant frustration with the System Center suite, where core functionality gets ignored (Just see the twitter verse every time someone wonders allowed why Hyper-V replication can't be managed by SCVMM) and sends us back into the wild swing that is the love/hate relationship of SCCM.