At a customer of mine a issue with Incident Requests in System Center 2012 R2 Service Manager was reported. Some users reported that they received the error:”Failed to execute Submit operation. Fix the reported error before… – The user <domain>\<accountname> does not have sufficient permission to perform the operation.
Full error in the console was:
System Center 2012 Configuration Manager Unleashed, the book on Microsoft System Center 2012 Configuration Manager is now generally available for purchase through Amazon and other shops.
I contributed two chapters to this book, and feel really honored to be part of the excellent line up of writers and contributors. I’ve written Chapter 9 on Client Management and Appendix B on extending Hardware Inventory.
Topics Covered in Chapter 9 include:
- ConfigMgr Client Requirements
- ConfigMgr Client Installation
- Client Assignment
- Client Health
- Client Settings
- Using the Resource Explorer
- Wake on LAN
Topics Covered in Appendix B: Extending Hardware Inventory include:
- How to extend Hardware Inventory
- Example of Extending Inventory
- Creating A Device Collection
Currently I already implemented several ConfigMgr 2012 and I must say I’m very pleased about the new Application Model and the new opportunities customers have for deploying applications.
I want to thank Kerrie Meyler who was the lead author for giving me this opportunity, and Steve Rachui for his technical review. And of course all the other Authors and Contributors for their feedback.
I’m currently working on a project where we implement a new ConfigMgr 2012 hierarchy in a forest where several ConfigMgr 2007 hierarchies already exist. The new ConfigMgr 2012 environment will be installed in a new domain within that existing Forest and we will not migrate any content from these ConfigMgr 2007 environments, but install every client using the OSD functionality of ConfigMgr 2012, but other deployment methods could be necessary for special scenario’s.
Even though this isn’t such a common scenario, I think the results of the test provide some insight on what you can expect in your own migration from ConfigMgr 2007 to ConfigMgr 2012, therefore I decided to share my findings. I hope it will be useful for someone reading this article.
Because one of the requirements for the implementation of ConfigMgr 2012 is that the impact on the existing environment should be as minimal as possible we did some test on what would happen if a ConfigMgr 2007 client would assign itself to a ConfigMgr 2012 environment and possible ways to prevent that.
- Install a ConfigMgr 2007 client when conflicting boundaries are configured on both ConfigMgr 2007 and ConfigMgr 2012
- Install a ConfigMgr 2007 client when there is only a boundary group with corresponding boundary defined in ConfigMgr 2012
- Install a ConfigMgr 2007 client and see what happens when it assigns to the ConfigMgr 2012 site and automatic client upgrade is turned on
- Install a ConfigMgr 2007 client and see what happens if only a boundary for Content Location in ConfigMgr 2012 is defined.
First there are some known and documented rules which we need to take into account:
A ConfigMgr 2012 client cannot attach itself to a ConfigMgr 2007 site. During Automatic Site Assignment, the ConfigMgr 2012 client will do a version check and when the site it tries to attach to isn’t at the correct level, it will fail to assign to that site.
In order to test the scenario’s, we build the following test environment
ConfigMgr 2007 Primary Site (pss1.nl.domain.local) in the NL child domain, with code N01
ConfigMgr 2012 Primary site (pss2.emea.domain.local) in the EMEA child domain, with site code E01