Quote of the Month
There are only two ways to live your life.
One is as though nothing is a miracle.
The other is as though everything is a miracle.
Albert Einstein
There are only two ways to live your life.
One is as though nothing is a miracle.
The other is as though everything is a miracle.
Albert Einstein
OCS Server Failed during forest Prepration although the domain prep worked fine.Reading the logs doesn’t turn up anything obvious in terms of what fields are not available.
Failure [0xC3EC78CA] At least one built-in display specifier object could not be found. Please make sure all display specifier objects were created successfully during DcPromo process by checking log files (%Windir%\Debug\Dcpromohelp.log and %Windir%\Debug\Csv.log).
Realizing that Prep Forest adds the required OCS containers, you may have a write error or you could have problems with your AD schema.
This issue may occur if the Display Identifiers object cannot be located in Active Directory.
To solve this problem:
1-Click Start, click Run, type cmd in the Open box, and then click OK.
2- Type the following command, and then press ENTER:
csvde -i -f %windir%\system32\mui\dispspec\dcpromo.csv -c DOMAINPLACEHOLDER domain distinguished name (DN) -j %windir%\debug -k
* Replace domain distinguished name (DN) in the command with the DN of the domain, such as dc=domain_name,dc=local.
For more Info check Microsoft KB
Micrsoft SCVMM team, Hyper-V team and BITS (Background Intelligent Transfer Service) team have just released two important updates to support SCVMM scenarios. Those updates is very important for all Hyper V hosts managed by SCVMM 2008 Beta.
This update resolves several issues to improve reliability when using SCVMM to manage you Hyper-V hosts.
Link To The Update: Hyper-V Update for Windows Server 2008 x64 Edition (KB956589)
You may face problem with installation of Hyper V Hotfix KB50050 on HP servers. You may be unable to configure Hyper-V on the HP server . After applying the hotfix the server will freeze with Configuring Updates 3 of 3 with 53%.
this issue might be related to the HP Network Configuration Utility was installed.
To take care of the issue, please follow the steps below:
1. Shut down the computer.
2. Insert the installation CD for Windows Server 2008, and then start the
computer from the CD.
3. Set your language preference, and then click Next.
4. Click Repair your computer.
5. Select the operating system that you want to repair, and then click Next.
Note You may have to provide disk controller drivers at this point. Click
Load Drivers, and then enter the location for the disk controller drivers.
6. In the System Recovery Options dialog box, click the operating system
that you want to repair, and then click Next.
7. In the Choose a recovery tool screen, select Command Prompt.
8. At the command prompt, type C:, and then press ENTER.
9. Type cd Program Files\HP\NCU, and then press ENTER.
10. Type ren cpqteam.dll cpqteam.dll.safe, and then press ENTER.
11. 1Type exit, and then press ENTER. The System Recovery Options screen is
displayed.
12. Click Restart.
13. When the server restarts, the configuration of Hyper-V automatically
continues.
14. When the configuration process is completed, follow these steps:
a. Open the “C:\Program Files\HP\NCU” folder.
b. Rename the Cpqteam.dll.safe file to Cpqteam.dll.
15. Restart the computer.
For more information, please view the URL below:
When you try to enable, disable, or update Hyper-V technology, the process stops responding
http://support.microsoft.com/kb/950792/en-us
To prevent this problem, uninstall the HP Network Configuration Utility before you enable, disable, or update Hyper-V.
You may got that error in SCVMM 2008 Beta when you start refresh library job:
An internal error has occurred trying to contact an agent on the server.domain.local
Ensure the agent is installed and running. Ensure the WS-Management service is installed and running, then restart the agent.
ID: 2912
Details: The server threw an exception (0×80010105)
This error is related to a known issue in SCVMM 2008 beta due to refresh rate for the library.
It will be fixed in RC relased in next month at 5 Oct.
To solve this problem you need to remove the VMMServer group + SYSTEM permissions from both the share permissions and the file permissions for this library server’s shares (so there are 4 entries to remove total).
The library refresher will ensure that the permissions on the share are correct each time it runs, so once you remove the permissions and refresh the share they will be back and everything will run normally.
Error (2927)
A Hardware Management error has occurred trying to contact server Server.domain.local
(Unknown error (0×80338112))
Recommended Action
Check that WinRM is installed and running on server foo.foo.com. For more information use the command “winrm helpmsg hresult”.
You may face this problem with SCVMM 2008 beta and Hyper V host. you have to verify that your Hyper-V server and your SCVMM 2008 server are at the same Hyper-V patch revision level.
This is becuase WinRM was modified with Hyper-V RC1.
If your Hyper-V box was updated to 90050 (the Hyper-V RTM) then your SCVMM server must have the SCVMM 2008 beta Hyper-V RC1 fix installed (and the 90050 patch installed).
So how do you know which version of Hyper-V you’re running?
The RTM release of Hyper is version number 6.0.6001.18016.
If you’re running Hyper-V on the full version of Windows Server 2008 you can open the Hyper-V manager then select the Help, About Hyper-V Manger. The version number 6.0.6001.18016 should be displayed in the About Hyper-V Manager dialog as you can see in the following Figure.
If you’re running Hyper-V on Server Core (or just prefer the command line method of doing things) then you can run the following command:
C:\>wmic datafile where name=”c:\\windows\\system32\\vmms.exe” get version
If you’ve got the current version of Hyper-V then you’ll see the following output:
Version
6.0.6001.18016
Where you connect to a global community of more than a billion people and nothing comes between you and a world of ideas and opportunities. With Windows on your mobile phone, PC, or the Web, walls begin to disappear—at home, at the office, and anywhere in between. You can balance work and life as well as fun and functionality. And with a wide range of software, services, and devices to choose from, your technology can be as unique as you are. That’s Windows. Life without walls.
If you’re part of the global PC community, we want to celebrate you. Visit I am PC site and share a photo or video and say a few words about what you love to do. We’ll add your photo to a gallery of people who’ve proclaimed “I’m a PC.” And you could appear in ads all across the web – maybe even on the big screen in Times Square!
The Hyper-V role enables you to create a virtualized server computing environment using a technology that is part of the Windows Server® 2008 operating system. This solution is provided through Hyper-V. You can use a virtualized computing environment to improve the efficiency of your computing resources by utilizing more of your hardware resources.
The Failover Clustering feature enables you to create and manage failover clusters. A failover cluster is a group of independent computers that work together to increase the availability of applications and services. The clustered servers (called nodes) are connected by physical cables and by software. If one of the cluster nodes fails, another node begins to provide service (a process known as failover). Users experience a minimum of disruptions in service.
When you build your lab by Microsoft document Step-by-Step Guide for Testing Hyper-V and Failover Clustering. You may face that error
The disk path is either not available, not accessible or can’t be managed by the cluster
I tried all solution…Checking the cluster configuration and failover between nodes. No Thing at ALL
After long time of Google it I found the solution: kb951308
This update incorporates changes in the way that the Windows Server 2008 Failover Cluster Management console functions for the Hyper-V role. These changes provide increased functionality and virtual machine controls that are consistent with the Hyper-V Manager console.
This update changes the Failover Cluster Management console (the Cluadmin.msc file) and the server components of the failover cluster. If this update is installed on one node, it should be installed on all nodes of a Windows Server 2008 failover cluster. It may be installed on one node at a time. However, we recommend having all the nodes updated in a reasonable time. You may experience errors on a Failover Cluster Manager that has not been updated to a failover cluster that has had this update applied. These errors occur because of differences between the non-updated Cluadmin.msc file and the updated failover cluster. Here we have the important part:
Allow for more than one virtual machine in a “Services or Applications” group
Before you install this update, only one virtual machine can be selected in the High Availability Wizard. Additionally, there is no method that you can use to add a virtual machine to a Services or Applications group by using the Failover Cluster Management console. After you install this update, the Failover Cluster Management console allows for more than one virtual machine. The High Availability Role Wizard for virtual machines identifies virtual machines that have files on the same disk and enables those virtual machines to be configured for High Availability. Therefore, the virtual machines will be in the same Services and Applications group. If the Services and Applications group moves to another node, all the virtual machines in that group are also moved.
After Apply the hotfix on both nodes and restart the cluster service on both..Opsss It works… Enjoy building your virtual lab
Later I would provide guide to build enterprise infrastructure using Hyper V Failover Cluster
Dan woodman wrote a new post about A New Choice in Virtualization
ANNOUNCING HYPER-V SERVER 2008!
Hyper-V Server 2008 is a new product from Microsoft, providing the functionality of the Hyper-V component in a standalone format. This product allows a “bare metal install.” That means that no operating system is required — Hyper-V Server is designed to be installed asthe OS on the host machine. It provides very limited functionality — only allowing the machine to host virtual machines. But, in a scenario like mine, that’s the only functionality I need. The best part is, Hyper-V Server 2008 is a free download. So, not only do you not need to use on of your Windows Server licenses to host virtual machines, but you don’t have to spend a penny!
I’m in the process of reloading my server with this new product, so expect more in the near future about the inner workings of Hyper-V Server 2008.
Just a week after my colleague Shanen Boettcher wrote about virtualization and its role in the Optimized Desktop, specifically announcing the RTM of Microsoft Application Virtualization 4.5, commonly called “App-V”, I’m proud to let you know that the entire MDOP 2008 R2 suite of products has officially reached RTM status! New and existing customers can get App-V 4.5 starting TODAY, and will be able to get the other MDOP 2008 R2 components the first week of October!
There are a lot of new and very useful upgrades and improvements in MDOP 2008 R2 in addition to last week’s upgrade to App-V 4.5