Time to migrate your 2007 SCCM envoirment to 2012. The first thing you might think of is how to push out the new client and how and when to configure boundaries.
First of all configure the client push settings on the 2012 site.
Then go to Installation Properties and configure the new 2012 site code:
SMSSITECODE=Sitecode and also i added my Fallback Status Point FSP=server.local This will tell the computer/client what site they will assign to.
Configure the boundaries at your new SCCM12 site and assign it to a boundary Group.
At this time you will now be able to push out the new client using client push or GPO. Remember to place the package to your DP.
Remember to uncheck the Auto assigment under Client Push Installation Properties, why? Because you don’t want both sites to auto assign their clients.
||Site assignment is used by clients that use automatic site assignment to find an appropriate site to join, based on the clients current network location. After a client assigns to a site, the client will not change that site assignment. For example, if the client roams to a new network location that is represented by a boundary in a boundary group with a different site assignment, the client’s assigned site will remain unchanged.When Active Directory System Discovery discovers a new resource, network information for the discovered resource is evaluated against the boundaries in boundary groups. This process associates the new resource with an assigned site for use by the client push installation method.
||Content location is used by clients to identify available distribution points or state migration points, based upon the client’s current network location
Ok so in the environment im working in right now, the SCCM site is working towards two different domains, lets call them “Domain A” & “Domain B”. I would like my Task Sequence to join the computers it the right domain depending on what default gateway they have on the network.
I have tried the following, but im afraid neither works:
Select * from Win32_NetworkAdapterConfiguration where DefaultIPGateway=’x.x.x.x’
This will not work because the adapters are stored in an array.
I also found a way to do this use this query:
Select * FROM Win32_IP4RouteTable
WHERE Destination=’0.0.0.0′ AND NextHop=’x.x.x.x’
This queries the routing table, no details about the adapter need to be known. It work’s great just in general and in query’s but it will not work in a Task Sequence.
Looks like i have to install MDT. Thank you for all your answers.
If you have Software Assurance on your WS2012 volume licenses then you can start downloading from the Microsoft Volume Licensing Service Center (VLSC). Those customers can start planning their Hyper-V (see the new features) host upgrades … but hold off if you are using System Center because you will need SP1 for System Center 2012 to continue to manage the upgraded hosts and migrated clusters.
It is not on MSDN/TechNet and is not expected there until after the launch on September 4th.@TechNetUK saw me tweeting on the subject and thankfully cleared up the issue:
I know, it’s very disappointing but that’s how the cookie is crumbling on this one. I’d love to have had it sooner so I could get current screenshots for the new WS2012 Hyper-V book.
Windows 8 is also available to VL w/ SA customers on the VLSC site.
SPLA folks, check your pricelists to ensure you are legit to move up first.
The Microsoft Partner Network download content has not been updated.
The System Center 2012 Service Pack 1 CTP2 includes updates to System Center 2012 for compatibility with Windows Server 2012 Release Candidate including support for Azure VM and capabilities for Hosted Service Providers.
This Community Technology Preview (“CTP2”) enables System Center customers to jointly evaluate System Center 2012 and Windows Server 2012 Release Candidate. CTP2 is for evaluation purposes only and not to be used in production as described in the EULAs associated with the product. No license keys are required to do this evaluation. CTP2 includes updates and enhancements to the following System Center 2012 components:
Virtual Machine Manager
- Improved Support for Network Virtualization
- Extend the VMM console with Add-ins
- Support for Windows Standards-Based Storage Management Service, thin provisioning of logical units and discovery of SAS storage
- Ability to convert VHD to VHDX, use VHDX as base Operating System image
- Support for Windows 8
- Ability to deploy Windows 8 Apps
- Real-time administrative actions for Endpoint Protection related tasks
Data Protection Manager
- Improved backup performance of Hyper-V over CSV 2.0
- Protection for Hyper-V over remote SMB share
- Protection for Windows Server 2012 de-duplicated volumes
- Uninterrupted protection for VM live migration
- Service Provider Foundation API to create and operate Virtual Machines
- Support for Azure VM; migrate VHDs from VMM to Windows Azure, manage from on-premise System Center
- Support for IIS 8
- Monitoring of WCF, MVC and .NET NT services
- Azure SDK support
- Support for Integration Packs, including 3rd party
- Manage VMM self-service User Roles
- Manage multiple VMM ‘stamps’ (scale units), aggregate results from multiple stamps
- Integration with App Controller to consume Hosted clouds
- Apply price sheets to VMM clouds
- Create chargeback reports
- Pivot by cost center, VMM clouds, Pricesheets
- Support for applications that create scheduled tasks during packaging
- Create virtual application packages from applications installed remotely on native server
The System Center 2012 CTP2 can be downloaded at : http://www.microsoft…s.aspx?id=30133
Technical Documentation for System Center 2012 CTP2 : http://www.microsoft…s.aspx?id=30134.
Supported operating systems: Windows 8 Release Preview, Windows Server 2008, Windows Server 2008 R2
The Virtual Machine Manager server for the CTP2 release System Center 2012 SP1 will only run on Windows Server 2012 RC
-via Technet > http://www.microsoft…s.aspx?id=30133
I stumbled in to this error message today when setting up a lab environment: “Current security context is not associated with an active directory domain or forest. ”
System.DirectoryServices.ActiveDirectory.ActiveDirectoryOperationException: Current security context is not associated with an Active Directory domain or forest.
at System.DirectoryServices.ActiveDirectory.DirectoryContext.IsContextValid(DirectoryContext context, DirectoryContextType contextType)
at System.DirectoryServices.ActiveDirectory.Domain.GetDomain(DirectoryContext context)
at Microsoft.ConfigurationManagement.AdminConsole.ActiveDirectory.Utils.TryParseSiteServerDomain(String domainName, String& ldapPath)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Solution? Log on with a domain account on your SCCM server, and not local administrator… :) ;)
If you are planning on installing Configuration Manager 2012 then before you do you need to be sure that your SQL collation is set to SQL_Latin1_General_CP1_CI_AS. If you live in the US then that’s probably what it is set to already but if not, and if you are using regional settings that may change the default collation (for example Swedish) then you will need to reinstall SQL from scratch to change the SQL collation or try some unsupported hacks to resolve your collation issues. If you are wondering why then it’s because ConfigMgr setup will not let you continue without the correct Collation. Full. Stop.
Configuration Manager 2012 requires SQL collation set toSQL_Latin1_General_CP1_CI_AS. Yup that’s it. And here’s where it states that on Technet. Expand the SQL Server Requirements section and look at the Collation field. And I quote: “The instance of SQL Server in use at each site must use the following collation: SQL_Latin1_General_CP1_CI_AS.”
If you have already install SQL and want to verify the collation settings prior to running ConfigMgr setup, then you can start SQL Server Management Studio and look at theServer Collation section of the General page as in this screenshot by right clicking on the database server and choosing properties.
How can i set the collation? If you are installing SQL server and want to set the collation manually, you can do so on the Server Configuration screen as pictured below, simply click on the collation tab.
Now you need to uninstall your SQL instance, this is what technet say about it: http://support.microsoft.com/kb/955499
- We recommend that you use the Add or Remove Programs feature in Control Panel to uninstall SQL Server.
Then install SQL again it might complain about reporting files that may be left over. Just ignore the reporting part of the SQL installation.