Install New Medv Med-v Med v server with Existing SQL Server

here is the POC configuration I have done with the enviroment below :

Machine 1 : WIndows server 2008 R2 – MEDV Server

IIS, SQL Server 2008 R2 Features Pack (CLR,Shared,Native Client )

Machine 2 : Windows Server 2008 R2 – SQL 2008 Enterprise

Default Setting .

After the installation of MEDV Server, I have proceed the cofiguration to setup the  Medv Reporting databse using another Server which a separte machine SQL server.

Full configuration kindly refer my Zip file at Skydrive


Posted in Uncategorized | 1 Comment

Remote App giving More Power and processor to specific Users / Groups

In Windows 2008 R2 , It come new exciting Feature call with Fair Share CPU Scheduling Features. Fair Share CPU Scheduling dynamically distributes processor time across sessions based on the number of active sessions and load on those sessions by using the kernel-level scheduling mechanism included with Windows Server 2008 R2.
In order for you to give exclusively resources for certain Group users or specific users, you can disable the  disable Fair CPU Sharing  feature by configuring the following registry entry

After you turn off the Fair Scheduling, next is to define who have the higher Priority where WSRM come into picture .

The administrator can allocate different CPU shares to different sessions using WSRM (Windows System Resource Manager). WSRM is an optional server feature used for managing system resource (processor and memory) usage. This feature has been part of the operating system since Windows Server 2008.

WSRM has a new built-in policy called “Weighted_Remote_Sessions”. This policy allows an administrator to categorize users into one of three priority groups: premium, standard and basic. WSRM ensures that users belonging to the premium group will get more CPU resources than those in standard, who will in turn get more CPU resources than users in basic.

You can use this feature by following the steps below.

  1. Open WSRM MMC (WSRM.msc). The “Weighted_Remote_Sessions” policy is listed under the “Resource Allocation Policies” node in the left pane. clip_image002
  2. To assign Users/Groups to different priority levels, right-click the “Weighted_Remote_Sessions” node and then select Properties. The Properties dialog looks like this:clip_image004
  3. Click Add to assign a priority to users or groups.
  4. In the next dialog, click Add to get the “Select Users or Groups” dialog.
  5. Choose the appropriate priority for selected users or groups, and then click OK:
  6. The added users are then listed in the Properties dialog:
  7. The Edit and Remove buttons are self-explanatory. Clicking OK saves the configuration created on the WSRM server.
  8. This information is not used unless “Weighted_Remote_Sessions” is set as the managing policy. If it is already set as the “Managing” policy, then new changes will take effect immediately. When you click OK in the Properties dialog, the new information is communicated to the service and WSRM updates the weights of only those sessions that are run by users whose category has been modified. If you want to update the weights of all running sessions on the server, select the “Update priority for all remote desktop sessions” check box.
  9. To set the Weighted_Remote_Sessions as Managing Policy, right-click its node in the left pane and select “Set as Managing Policy.”
  10. If some other policy is in the managing state, then setting “Weighted_Remote_Sessions” policy as managing shows you a dialog stating that you will need to restart the WSRM server to make this policy active. If you click Yes, the WSRM server is restarted.
  11. If Weighted_Remote_Sessions is in a managing state, then setting some other WSRM Policy in managing mode again requires a restart of the server.

Weight Remote Sessions configuration Reference from Msdn side :

Posted in Uncategorized | Leave a comment

Remote App session that never expired and never die

I came across this question today when I meet up customer today .

Customer that in in Software Development department wanted their engineering application will not die forever even they shutdown the PC and back home.

Here is the solution that you might consider if you want your Remote app session will not disconnected forever or within long hours or Days

Session Time Limits policy settings for Terminal Services sessions to set the time limit for RemoteApp sessions.

in Windows Server 2008 have one new Policy Setting that allows for the administrator to set the time delay for the logoff from a disconnected RemoteApp session. There only things to take care this might overwhelming server resources by permitting these “no remote program running” RemoteApp sessions to remain in a disconnected state.

To locate the session time limit policy settings, follow these steps:

1. Log on to the terminal server as an administrator.

2. Start the Local Group Policy Editor. To do this, click Start, click Run, type gpedit.msc, and then click OK.

3. Locate the following node:

Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Session Time Limits

Note: The policy settings are also located under User Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Session Time Limits

4. The new policy—Set time limit for logoff of RemoteApp sessions—is shown in the following figure:

How do I enable the time limit for logoff delay?

To enable the “Set time limit for logoff of RemoteApp sessions” policy setting, follow these steps:

1. In the right pane of the Local Group Policy Editor, double-click Set time limit for logoff of RemoteApp sessions.

2. Click Enabled.

3. In the RemoteApp session logoff delay list, select the desired time for logoff delay, and then click OK.

4. At a command prompt, type gpupdate, and then press ENTER to force the policy to refresh immediately on the local computer.

After the policy setting is enabled, disconnected RemoteApp sessions will be logged off after the configured time delay.

Posted in Uncategorized | Leave a comment

Hello world!

Welcome to This is your first post. Edit or delete it and start blogging!

Posted in Uncategorized | 1 Comment

MED-V MED V Deployment for Multiple user accessing same PC


MED-V – The image has been downloaded or imported by a different Windows user


If you faced this error code most likely you have try to access the MEDV image using different credential who downloaded the First Image .


and if you planning to let the MEDV image support multiple user , here is the few trick that you can consider , I have help one of the customer to deploy this legacy application which running in Windows 2000 


1. Change the Security Permission for your “MEDV IMAGE FOLDER “ … Only user activates and extracts the MED-V Workspace image to the local host can use that . The activating user is the only user that can use that workspace. For multiple users to have access to the same MED-V VM, the ACLS need to be modified for “C:\MED-V Images”. On the Security tab, add  Domain USERS have the READ and WRITE permissions for C:\MEDV Image Folder …


2. After you do this , when you log in another user you will face the error

“This workspace was last accessed by a different user. If you continue, the Workspace will be restarted, losing the machine state that was saved by the last user.” This is because the previous user have logged in and even you restart the session is being locked.


3. What I have do is I created a logoff script for end user to logoff after they using MEDV. I just create it as a shortcut application that for those who wanted to logoff.

4. When I log in as administrator for the first time setup ,  I will complete the entire VM setup with domain join and everything, then I will run the log off shortcut, this will allows me to log off my current domain account and leave the PC clean to the next USER. When it go to anyone who I wanted to deply MEDV .

THE COMPUTER WILL Like a new PC to the new user without any error code…

Posted in Uncategorized | Leave a comment

MED-V unblocking and accelerating Windows 7 Migration .


My Presetnation Slides of MED-V during TEchinsight Penang

Posted in Uncategorized | Leave a comment

APPV “The installation program could not connect to the configuration data store…. Please see install log…..

Thanks TIM For sharing this work around .


Launched SqlServer Management Studio Express

  • Expand the "Security" object and Expand the "Logins" object on the left.

  • Modified (Domain Users Pofile with add "sysadmin" role, and ENABLE  "db_owner" membership to the "master", "model", "msdb", and "tempdb" databases. 

  • Restart SQL Server Express Services

  • after Restart then you will able to see LOCALHOST\SQLEXPRESS in your DB

copy from

Posted in Uncategorized | Leave a comment