Recently I did an upgrade of a ConfigMgr 2012 R2 SP1 environment to ConfigMgr Current Branch (1511). I did the following upgrades during the day (with some time and checks between them):
ConfigMgr server (1):
-Windows Server 2012 to Windows Server 2012 R2
SQL server (1):
-Windows Server 2012 to Windows Server 2012 R2
-SQL server 2008 R2 SP2 CU4 to SQL Server 2014 SP1
Site systems (3):
-Windows Server 2012 to Windows Server 2012 R2
ConfigMgr server (1):
ConfigMgr 2012 R2 SP1 to ConfigMgr Current Branch (1511)
This based on the following recommendations:
-ConfigMgr supports an in-place upgrade of the Operating System of the site server in the following situations: In-place upgrade from Windows Server 2012 to Windows Server 2012 R2
-When your version of ConfigMgr supports SQL Server 2014, ConfigMgr supports the in-place upgrade of SQL Server to SQL Server 2014 with the following limitations: Each ConfigMgr site must run a version of ConfigMgr that supports using SQL Server 2014 before you can upgrade to SQL Server 2014 at any site.
Source: Supported Upgrade Paths for Configuration Manager
After this upgrade(s), where everything did go fine, the default management wouldn't start anymore. This because of the error: HttpSendRequestSync failed for port 80 with status code 500 (mpcontrol.log).
Furthermore the Application Catalog didn't function also anymore. This because of the error: Component file list item in the install map for component SMS_DMAPPSVC_CONTROL_MANAGER does not contain srvboot.exe (sitecomp.log).
I did also get a error message during deployment: The Windows Boot configuration data file does not contain a valid OS Entry. Error code: 0xc0000098. Let's say: I wasn't amused here :-)
I did the following actions on the site system:
-Removed the management point and install it again
-Restarted MP component(s) in ConfigMgr Service Manager
-Restarted DP component(s) in ConfigMgr Service Manager
-Removed ASP.NET 4.5 (IIS) and install it again
-Checked if "Enable 32-Bit Applications" (IIS) was set to FALSE
-Removed both Application Catalog roles (still uninstalled)
-Checked if MP computer account is a member of MP Role (msdbrole_MP) in the SQL database.
-Restarted both ConfigMgr and SQL servers
But what I did, the error message came back everytime. In the end I removed the management point, and installed a new one on another server. This one was working immediately. Does anyone has a clue to resolve this at later time? Hope that the management point can be restored to the original location later!
This drives my crazy for multiple days now..
More websites about this topic:
The Windows Boot configuration data file does not contain a valid OS Entry
MP Control Manager detected management point is not responding to HTTP requests
SCCM MP Internal Server Error ISS Call to HttpSendRequestSync failed for port 80 with status code 500
Update 17-2: Thanks for comments already!
-The management point can be fixed when both MP and IIS role are removed. Reinstall them should be the solution. (to be continued)
-The application catalog can be fixed when copying the line "FILE <srvboot.exe><0><3667640>" and placed it into the SMS_DMAPPSVC_CONTROL_MANAGER component of install.map.
Update 2-3: After removing both roles (management point and application catalog) I removed IIS (and BITS) completely for the ConfigMgr server. After a required reboot I installed IIS (and BITS) again. After that both roles were installed successfully at first try. IIS re-install did it again :-)
When starting OS deployment from ConfigMgr you get the following error message: The Windows Boot configuration data file does not contain a valid OS Entry. This because Windows Deployment Services (WDS) has been manually configured at some point. The best course of action at this point is to reset the installation of WDS by reinstalling the PXE Service Point and WDS.
What also can be the cause is that deployment is started on an unknown system, and Enable Unknown computer support isn't checked at the Distribution Point settings. Just select this option and deploy a task sequence to All Unknown Computers collection too. After that your headache will be gone :-)
Source: Gerry Hampson Device Management (comments)
Last week I posted a setup for installing Windows 8 on a VHD (Virtual Hard Disk). Have a look for that here: Guide to install Windows 8 on a VHD. Now I received some questions how to make the Windows 8 setup undone, so Windows 7 will be the default Operating System again. In this blog I will give some solutions for this!
First it's possible to make Windows 7 the default Operating System again, without removing the Windows 8 installation. This is the easiest one to configure. Just boot from hard disk then, and while on the "Choose an Operating System" screen select "Change defaults or choose other options".
Then select "Choose the default operating system" to select Windows 7 as default OS again. It's also possible to change the default timer (from 30 seconds to 5 seconds) for faster boot there.
That way another boot menu will be used (from Windows 7 OS) which is must faster for booting Windows 7 AND Windows 8. I prefer this one because it's faster, not for the better menu.
Now another solution for totally remove Window8 from the boot menu. There are a few possibilities to make this possible:
- Use BCDEDIT and remove the Windows 8 boot entry
- Rebuild the boot menu from the Windows 7 DVD repair option
- Use BCDBOOT to repair boot files or create a new BCD store
It's of cource possible to remove the VHD file from hard disk. Then the boot menu will not be changed, and when selected "Windows 8" an error will follow:
Nothing to worry about, but not the better solution. It can be still part of a solution when using BCDEDIT, Windows 7 repair option or BCDBOOT. I will explain them all now.
With BCDEDIT many options comes available to add, delete, edit, and append entries in the boot configuration data (BCD) store. The BCD store contains boot configuration parameters and controls how the operating system is booted.
When not sure about BCDEDIT command first create a backup with: BCDEDIT /Export C:\BCDCOPY. Then delete the Windows 8 entry with the BCDEDIT /Delete command. For doing that the Identifier is needed. This can be found with the BCDEDIT command (without parameters):
The command for deleting Windows 8 here (in my case) is BCDEDIT /Delete {3b0c2878-9f48-11df-8e48-a2ba939022f2} /Cleanup. Let's have a try! I've deleted the Windows 8 entry and Windows 7 is booting immediately after reboot. Exactly what I want. No need to display the 30 seconds timer anymore, because there's only a single OS left.
When running BCDEDIT again my Windows 8 entry is gone, and Windows 7 will be the only OS left to boot. When I want to go back to Windows 8 again I choose: BCDEDIT /Import C:\BCDCOPY to have it all functional again.
The second solution is the Windows 7 repair option. Just start from a Windows DVD and choose "Repair your computer". Then select your OS (Windows 7) and choose "Startup Repair". The boot manager will then be repaired, and Windows 7 will be the default OS again. That way no rollback to Windows 8 is possible, because a clean boot manager is created.
If you click on “Startup Repair” then Windows will scan your system for common errors and will hopefully figure out that your boot manager is broken. A simple solution and maybe the most effective?
At last there is the BCDBOOT command. With BCDBOOT it's possible to copy critical boot files to the system partition and to create a new system BCD store.
I'm not that familiar with BCDBOOT, but for more information about this there is a TechNet post available: BCDboot Command-Line Options. It seems the most effective for creating a new BCD store or to add boot options to an existing BCD store.
For example, to create a BCD store on the default system partition with the optional locale parameter set to US English, you would use the following command: BCDBOOT C:\Windows /l en-us
Hope you have enough tools by now to remove Windows 8 from the boot menu and re-use Windows 7 as the only OS installed (if needed).
