Search This Blog

Loading...

Wednesday, March 31, 2010

Upgrade SCCM 2007 to SP2

I just upgraded SCCM 2007 SP1 to R2 and SP2. A bit late since it released. Anyway, here is the information that you should take note.

The upgrade path is either
a) SCCM 2007 SP1 > R2 > SP2 or
b) SCCM 2007 SP1 > SP2 > R2

SCCM 2007 R2 is just an additional features added so you can install before or after SP2. Before you upgrade to SP2, i recommend that you perform SCCM backup first. For more info, please refer to http://www.ms4u.info/2009/07/part-106-backup-sccm.html

Once you have complete the backup, you need to uninstall existing WAIK as it is not compatible. The SCCM SP2 will run pre-requisite check and give you warning about WAIK. Then proceed to download WAIK Windows 7 from http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=696dd665-9f76-4177-a811-39c26d3b3b34

After the WAIK installation is complete, you can proceed to install SCCM SP2. The installation went smooth and complete without any error. To verify , open the Configuration Manager Console.

1. Check the version. Go to Site Database > Site Management > Your Site Code > Right Click > Properties


Reference:-
Make sure, it is listed as 4.00.6487.2000.

2. From the figure above, verify the SMS Provider location is displaying your SCCM computer name. I noticed the SMS Provider location is not display after the upgrade. To solve this problem, go to Start > All Program > Microsoft System Center > Configuration Manager 2007 > ConfigMgr Setup. Select
Perform site maintenance or reset this site and select Modify SMS Provider Configuration.

That should do the trick.

3. If you perform operating system deployment, make sure the default boot image has updated as well.
In System Center Configuration Manager 2007 expand the Operating System Deployment node > boot images > select your X64 / x86 boot image and review it's properties, the version should read 6.1.7600.16385. I will skip this first as i did not perform operating system yet.

Stay Tuned for more update on SCCM Upgrade.


Sunday, March 28, 2010

Error while connecting to the reporting server. Ensure that Virtual Machine Manager management pack and its reports are installed on the Operations Manager server. ID: 3451

You will encounter this error message when configure reporting for Virtual Machine Manager (VMM)
Error message:-
Error while connecting to the reporting server. Ensure that Virtual Machine Manager management pack and its reports are installed on the Operations Manager server. ID: 3451

Strange ! VMM 2008 R2 MP is by default available when you run "Configure Operation Manager". Why the system is asking again? Weird but here is the workaround that i use to solve this issue.

Workaround:-

Step 1:-Configure setspn and set special permission for SDK Account.

a) Logon to a domain controller within the domain with Domain admin rights

b) Use Command prompt and run the following command

Setspn.exe –A MSOMSDK/ OMservername.FQDN domain\SDKAccount (this is the SDK service account name)
Setspn.exe –A MSOMSDK/ OMservername domain\SDKAccount

Note:- To verify, run setspn -L OMservername
b) Run ADSIEdit.msc as a domain admin.

c) Find the SDK account, right click, properties.

d) Select the Security tab, click Advanced.

e) Click Add. Type “SELF” in the object box. Click OK.

f) Select the Properties Tab.

g) Scroll down and check the “Allow” box for “Read servicePrincipalName” and “Write servicePrincipalName”






















h) Click OK three times.

i) Restart your SDK service – if AD has replicated from where you made the change – all should be resolved. The best is restart DC, VMM and Operation Manager.

Step 2 : Check Reporting URL (if still not available)
 
a) The Reporting URL must match between VMM and Operation Manager. To verify, on the Operation Manager Console, go to Administration > Settings > Reporting.

b)You will get your Reporting URL. Enter the same URL in the VMM console. Then, try use browser and access the Reporting URL. Verify that you can access the reporting and "System Center Virtualization Report 2008 R2" is available.

Step 3:- Verify System Center Virtualization Report 2008 R2 Report
a) On Operation Manager Console, Click on Reporting pane, do you see System Center Virtualization Report 2008 R2? Inside this report, consist of 5 reports for Virtualization.

b)If you did not see "System Center Virtualization Report 2008 R2", i advise that you perform uninstall of VMM console on the Operation Manager server. Then rerun "Configure Operation Manager" (available on VMM CD). After finish the installation, wait for a while before the report start to populating. Just keep refresh until 5 reports show up.

That should solve the problem. :)

Friday, March 26, 2010

Support Earth Hour 2010

Let come together and support Earth Hour.

Date: 27 March 2010
Time: 8.30 -9.30 PM
Events: Switch off your light for an hour. :)

For more information about Earth Hour, please click on this link:- http://www.earthhour.org/

Wednesday, March 24, 2010

Demo: DPM 2010 RC for Virtualization Host

Hi guy,

Here is some demo about DPM 2010 RC products which i have prepare during MVUG March 2010 meeting. To join our communities, pls go to http://www.facebook.com/group.php?gid=216237734803 .

To view in another windows, please click into the video.
a) Initial Configuration


b)Backup Hyper V using DPM 2010 RC


c)Recover Hyper V using DPM 2010 RC


d)Item Level Recovery using DPM 2010 RC


e)Extra:- Backup using Windows Server Backup for Hyper V


Enjoy!

Monday, March 22, 2010

Presentation:- Backup and Recovery for Hyper V R2

Here is the presentation video for MVUG March 2010 meeting.

Presentation:- Backup and Recovery for Hyper V R2 System - Part 1


Presentation:- Backup and Recovery for Hyper V R2 -Part 2


Presentation:- Backup and Recovery for Hyper V R2 - Part 3


Demo Video will be uploaded soon. Stay Tuned!

Friday, March 19, 2010

Microsoft Desktop Virtualization Hour

For those who has missed and sleep during this event.

Pls visit the link below to learn more on latest technology. VDI is a new way to move forward..Are you ready for it?

http://www.desktopvirtualizationhour.com/

Feel excited !

Please read more from http://www.microsoft.com/Presspass/press/2010/mar10/03-18DesktopVirtPR.mspx about the new changes.

Tuesday, March 16, 2010

Part 2:- Building VDI using Remote Desktop Services (RDS)

Here is the Part 2 of Building VDI using Remote Desktop Services (RDS). For those who has missed Part 1, please click on this link :- http://www.ms4u.info/2010/03/part-1-building-vdi-using-remote.html

Continue from Part 1. This part will focus on installing each RD roles before start the actual configuration.

Task 1: Install Remote Desktop Virtualization Host role

On the RDSVH, install Hyper V roles and Remote Desktop Virtualization Host. You need to install RD Virtualization Host role for each Hyper V server that's hosting Personal or Virtual Desktop Pool

1. Log on to RDSVH with administrative right.
2. Open Administrative Tools. Click Start > Administrative tools > Server Manager
3. Right click Roles and select Add Roles
4. On the Before You Begin page, Click Next
5. On the Select Server Roles page, select Hyper V roles and Remote Desktop Service and then click Next
6. On the Remote Desktop Service page, click Next
7. On the Select Role Services page, select Remote Desktop Virtualization Host and click Next
8. On the Confirm Installation selection page, Click Install
9. Restart the system when asked.

Task 2: Install Remote Desktop Session Host (Redirector) role

1. Right click RDSRedirect VM and select Connect
2. Log on with administrative right
3. Open Administrative Tools. Click Start > Administrative tools > Server Manager
4. Right click Roles and select Add Roles
5. On the Before You Begin page, Click Next
6. On the Select Server Roles page, select Remote Desktop Service and then click Next
7. On the Remote Desktop Service page, click Next
8. On the Select Role Services page, select Remote Desktop Session Host and click Next
9. On the Uninstall and Reinstall Applications for Compatibility page, Click Next

Note that the purpose of installing the RD Session Host role service for this solution is for it to act as a Redirector and not for RemoteApp publishing.

10. On the Specify Authentication Method For Remote Desktop Session Host page, select "Require Network Level Authentication" and click Next. Your client must be running minimum Windows XP SP3 (with some configuration that you need to perform) or later in order to support Network Level Authentication. I'm talking about your offsite computer (that's what i mean).

11. On the Specifying License Mode, select Configure Later and Click Next. You can run RDS for 120 days before activating the license. Remember to get the license before the expire date.
 
12. On the Select User Groups Allowed Access to this RD Session Server, click Add button and Enter VDIGroup.
13. Click Check name and click Ok button.

14. Click Next
15. On Configure Client experience, leave default value and click Next
16. Review the confirmation page and Click Install button
17. Click Close button and select Yes to restart the system.

Task 3: Install Remote Desktop Connection Broker role

1. Right click RDSBroker VM and select Connect
2. Log on with administrative right
3. Open Administrative Tools. Click Start > Administrative tools > Server Manager
4. Right click Roles and select Add Roles
5. On the Before You Begin page, Click Next
6. On the Select Server Roles page, select Remote Desktop Service and then click Next
7. On the Remote Desktop Service page, click Next
8. On the Select Role Services page, select Remote Desktop Connection Broker and click Next
9. Review Confirm Installation selection and click Install button. The installation process will begin.
10. Click Close button

Task 4: Install Remote Desktop Web Access & Remote Desktop Gateway role

1. Right click RDSGatewayWeb VM and select Connect
2. Log on with administrative right
3. Open Administrative Tools. Click Start > Administrative tools > Server Manager
4. Right click Roles and select Add Roles
5. On the Before You Begin page, Click Next
6. On the Select Server Roles page, select Remote Desktop Service and then click Next
7. On the Remote Desktop Service page, click Next
8. On the Select Role Services page, select Remote Desktop Web Access and Remote Desktop Gateway
9. Click Add Required Role Service button
10. Click Next
11. On the Choose a Server Authentication Certificate for SSL Encryption page, select Create a self-signed certificate for SSL encryption, and then click Next.
It is recommended to get a 3rd party certificate/External Certificate.

12.On the Create Authorization Policies for RD Gateway page, select Now, and then click Next.

13. On the Select User Groups That Can Connect Through RD Gateway page, click Add. In the Select Groups dialog box, specify VDIGroup, and then click OK to close the Select Groups dialog box. Click Next.

14. On the Create an RD CAP for RD Gateway page, enter the name VDI-RD_CAP_01 for the Remote Desktop connection authorization policy (RD CAP), select Password, and then click Next.


15. On the Create an RD RAP for RD Gateway page, enter the name VDI-RD_RAP_01 for the Remote Desktop resource authorization policy (RD RAP), and then select Allow users to connect to any computer on the network. Click Next.

Note: You can limit user to connect computer on the network. If you would like, you can create a VDI computer group and put the computer pool into this group.

16. On the Network Policy and Access Services page (which appears if this role service is not already installed), review the summary information, and then click Next.
17. On the Select Role Services page, verify that Network Policy Server is selected, and then click Next.
18. On the Web Server (IIS) page, click Next
19. On the Select Role Service, accept the default setting and click Next
20. On the Confirm Installation Selection Page, click Install button. The installation process will begin.
The default URL is https://RDSGatewayWeb/RdWeb . Use this url for accessing the VDI.

21. On the Installation Results page, review the results and click Close

Click here for Part 3:- Building VDI using Remote Desktop Services (RDS)

Active Directory Schema for Personal Virtual Desktop Pool on VDI

Some information about Active Directory Schema for Personal Virtual Desktop Pool

Personal virtual desktops do need a Windows Server 2008 or Windows Server 2008 R2 schema. What does this mean is, you need to upgrade your schema to at least Windows Server 2008.

Here are the Active Directory requirements for personal virtual desktops:

To deploy personal virtual desktops, your schema for the Active Directory forest must be at least Windows Server 2008. To use the added functionality provided by the Personal Virtual Desktop tab in the User Account Properties dialog box in Active Directory Users and Computers, you must run Active Directory Users and Computers from a computer running Windows Server 2008 R2 or from a computer running Windows 7 that has Remote Server Administration Tools (RSAT) installed.

You must use a domain functional level of at least Windows 2000 Server native mode. The functional levels Windows 2000 Server mixed mode and Windows Server 2003 interim mode are not supported.

Sunday, March 14, 2010

Pre-requisite require when backup using DPM 2010 RC

When creating Protection Group in DPM 2010 RC console, you will see the following error message

















The error message is quite straight forward. Since my Hyper V host is running on Windows Server 2008 R2, i need to go to the following links as requested
http://support.microsoft.com/kb/975921
http://support.microsoft.com/kb/975354

Both links point to request a hotfix from Microsoft. After request is make, the hotfix is available for download.

Install two hotfixes and you need to restart the Hyper V hosts after apply the hotfixes. Once the host has restarted, you need to go to Management and select agent tab using DPM 2010 console.
Refresh all the entire Hyper V host and make sure the status indicated "OK".

Once you have complete this process, you can start to create the protection group without encounter any problem.

Saturday, March 13, 2010

Installing DPM 2010 RC

The installation step is almost the same as DPM 2010 Beta. You can refer to http://www.ms4u.info/2009/10/installing-dpm-2010-beta.html .

For those, who has install DPM 2010 into Windows Server 2008 R2, you will notice this error on DPM 2010 Beta: http://www.ms4u.info/2009/11/dpm-2010-beta-failed-to-install-in.html . Microsoft has fixed this issue and the installation completed without any error.

However, once you have restart the DPM server and you try to access the DPM console, you will receive this error message:- "Unable to connect to DPM (IDM:948)"












So i have decided to check on the DPM service. DPM service is dependent to SQL Express and i have found that the SQL service failed to start when using the assigned account.
















Workaround:-
To fix this issue, i have set both SQL server services to Local system account. Then restart the SQL services and DPM services.

Note:- This problem not happen all the time.

Thursday, March 11, 2010

Video:- Building a Failover Cluster and Live Migration for Hyper V

Hi,

I have created a video on how to build a failover cluster and live migration as part of community contribution for Malaysia Virtualization User Group (MVUG) March 2010 meeting.

Click on the video to open another browser for ease in viewing.

Presentation:- Building a Failover Cluster and Live Migration - Part 1


Presentation:- Building a Failover Cluster and Live Migration - Part 2



Presentation:- Building a Failover Cluster and Live Migration - Part 3



Presentation:- Building a Failover Cluster and Live Migration - Part 4



Demo:- Building a Failover Cluster and Live Migration



Enjoy!

Sunday, March 7, 2010

Part 1- Building VDI using Remote Desktop Services (RDS)

Hi Visitor,

I found out that not many documentation writing about "Building VDI using Remote Desktop Services (RDS)" from beginning until the end. So I 've decided to share the configuration step by step that I have configured in my environment. I will break down into several parts as the configuration is quite long and complex. Trust me ! It's not easy and hopefully by following my step by step instruction , you will be able to deploy VDI in your environment as well.

I have spent few days to perform "R and D" and finally managed to publish VDI to the Internet (Public) and user can access office environment by using browser. All you need to do is open port 443 (TCP/HTTPS) in order for user to access to the Virtual Desktop Infrastructure (VDI).

Below is the figure of the infrastructure that I have setup:-

By using Hyper V R2 and SCVMM 2008 R2, I have created the following Virtual machine

In this setup, I'm going to use Windows 7. You can setup client VM running on

○ Windows 7 Business, Enterprise or Ultimate,
○ Windows Vista with SP1 - Business, Enterprise or Ultimate,
○ Windows XP Professional with SP 3

I have tested on these above operating system and it work like a charm. If you would like to know more about the different between Personal and Virtual Desktop Pool, please refer to http://www.ms4u.info/2010/02/revealed-microsoft-virtual-desktop.html . To make it more interesting, VDI01-Win7.ms4u.info is set to Personal Virtual Desktop and assigned to VDIUser1 which only use Office2007 whereby the Virtual Desktop Pool will use Office 2010 (Beta).

The Client VM name on the Hyper V host should be FQDN and identical as the computer name in the VM.

Example: VDI01-Win7 is the computer name

VDI01-Win7.ms4u.info is the FQDN










For easy and faster deployment of the VM, I using VMM feature called "Rapid Provisioning Virtual machine using Template". For those who are not familiar with this feature, please refer to http://www.ms4u.info/2009/11/rapid-provision-virtual-machine-with.html

Let start to look into initial configuration:-

MS4UDC - Domain controller

You may want to take note on some criteria to deploy personal virtual desktop . Your Active Directory need functional level running in Windows 2008. To use the added functionality provided by the Personal Virtual Desktop tab in the User Account Properties dialog box in Active Directory Users and Computers, your functional level for AD DS must be set to Windows Server 2008 R2.

Task 1:- Create user account for VDI

1. Log on to MS4UDC VM
2. Go to Start > Program > Administrative Tools > Active Directory Users and Computers
3. Right click Users container , select New and User
4. Enter username :- vdiuser1 and click Next


















5. Enter password :- P@ssw0rd , uncheck "User must change password at next logon" and click Next
6. Click Finish
7. Repeat step 3 to 6 to create user account for vdiuser2 and vdiuser3.

Task 2:- Create a group for VDI

1. Right click Users container , select New and Group
2. Enter the group name: vdigroup with Group scope:- Global and Group type: Security and Click Ok button


















Task 3: Assign user account to VDI group

1. Right click Vdigroup and select Properties
2. Click on Members tab and select Add button
3. Enter vdiuser1,vdiuser2 and vdiuser3 and Click Check name
4. Click Ok button
5. Click Ok button to close the vdigroup properties


 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
   
Click here:- http://www.ms4u.info/2010/03/part-2-building-vdi-using-remote.html for Part 2:- Building VDI using Remote Desktop Services (RDS).

Friday, March 5, 2010

TechNet Virtual Lab: Implementing Citrix XenDesktop 4 on Hyper-V R2

This lab is intended for IT Professionals who would like to deliver virtual desktop computers using Microsoft Hyper-V Server, Microsoft System Center Virtual Machine Manager and Citrix XenDesktop. Users will work through the steps to simulate deploying multiple virtual desktops, and will first capture a reference image using the Citrix Provisioning Server for Desktops. Next, the user will verify that the computer can be booted from a diskless client computer. The user will create multiple virtual machines using the reference computer as a template. Finally, the user will use the Citrix Desktop Delivery Controller and System Center Virtual Machine Manager to create a group of virtual desktops and deploy them to end devices. At the end of this lab, the user will have worked through all the steps required to implement Citrix XenDesktop using Microsoft System Center Virtual Machine Manager and Microsoft Hyper-V Server.

Check it out:- https://cmg.vlabcenter.com/default.aspx?moduleid=281742e3-2613-42da-bd58-2c3578f039b4

Wednesday, March 3, 2010

Setup failed to install SMS Provider

Sometimes when you install SCCM and the database is located on remote server, you will get this error message "Setup failed to install SMS Provider".

Workaround:-
Execute this command on SCCM server.

setspn -A MSSQLSvc/myserver.mydomain.com:1433 mydomain\accountname


In this example, "myserver" is the host name of the server that is running SQL Server, "mydomain" is the Windows domain name, and "accountname" is the domain account under which SQL Server is running.