Nelson Araujo's WebLog https://docs.microsoft.com/archive/blogs/nelson_araujo/feed.xml Your source for research in the cloud. Wed, 17 Apr 2019 03:25:09 GMT en-US hourly 1 Welcome to Cloud Research Engagements https://docs.microsoft.com/archive/blogs/nelson_araujo/welcome-to-cloud-research-engagements Mon, 08 Feb 2010 15:52:00 GMT https://blogs.msdn.microsoft.com/nelson_araujo/2010/02/08/welcome-to-cloud-research-engagements/ We are going through fundamental shift in basic research in most academic disciplines from the three traditional paradigms of theory, experiment and computation, to a new fourth paradigm of data-driven discovery.

Read more @ https://research.microsoft.com/en-us/groups/ccf/engagements.aspx

]]> Virtual Server 2005 – IDE to SCSI Virtual Machine Migration https://docs.microsoft.com/archive/blogs/nelson_araujo/virtual-server-2005-ide-to-scsi-virtual-machine-migration Mon, 15 Jan 2007 18:36:00 GMT https://blogs.msdn.microsoft.com/nelson_araujo/2007/01/15/virtual-server-2005-ide-to-scsi-virtual-machine-migration/ The following white paper contains important information on how to migrate your Virtual Server hard disks from IDE to SCSI. That will increase the overall performance of your virtual machines. If you have any questions, don't hesitate to ask! Enjoy.

https://www.microsoft.com/downloads/details.aspx?FamilyId=8D71F23D-0380-4C2F-81DF-6F96ABE05493&displaylang=en

]]> MSDN Wiki pages https://docs.microsoft.com/archive/blogs/nelson_araujo/msdn-wiki-pages Thu, 15 Jun 2006 20:06:00 GMT https://blogs.msdn.microsoft.com/nelson_araujo/2006/06/15/msdn-wiki-pages/ Microsoft released a Wiki for MSDN. You can check them here: https://msdnwiki.microsoft.com/

My contributions to the Wiki can be found here: https://msdnwiki.microsoft.com/wikiedit/myprofile.aspx?name=Nelson%20Araujo&skinlocale=en-us

]]> Updating a template https://docs.microsoft.com/archive/blogs/nelson_araujo/updating-a-template Tue, 04 Apr 2006 00:26:00 GMT https://blogs.msdn.microsoft.com/nelson_araujo/2006/04/04/updating-a-template/ Due to the way the file system is organized into the disk, it is not possible to patch the disk on the parent without invalidating (thus destroying all modifications made since then).

The recommended procedure to update a template would be:

  1. Create a new Virtual Machine from a template
  2. Install updates and make any other changes you wish
  3. Save & Commit the VM
  4. Move the updated VHD file to the template folder (with another name different from the current template)
  5. Update the <Template> entry with the information
    • Change the ID of the template
    • Add the same path
    • Keep the same <Name> & <Description>
  6. Mark the original template as disabled

After that any new VM created will use the new template. You can use the report on the Administration section to monitor when the old template is idle

  • Delete the original template when it is idle
]]> Installing VSDM on a 64-bits Windows Server System 2003 https://docs.microsoft.com/archive/blogs/nelson_araujo/installing-vsdm-on-a-64-bits-windows-server-system-2003 Thu, 09 Feb 2006 18:04:00 GMT https://blogs.msdn.microsoft.com/nelson_araujo/2006/02/09/installing-vsdm-on-a-64-bits-windows-server-system-2003/ VSDM works on a 64-bits system. To enable it the system needs to be correctly configured. Please follow the steps below to enable VSDM to run on those systems.

System Requirements

  1. Install Virtual Server 2005 AMD64
  2. Install .NET Framework 1.1
  3. Install .NET Framework 1.1 Service Pack
  4. Execute the following command from a Command Prompt window:
    cscript %SystemDrive%\inetpub\AdminScripts\adsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 1

Security: Do not forget to visit Windows Update (or Microsoft Update) to make sure all the installed software is up-to-date with the latest critical security patches available.

Installing VSDM

After you meet the requirements above, follow the normal installation and configuration of VSDM. No other changes are necessary to run VSDM on a 64-bits system other than configuring the server correctly.

]]> Automating VSDM via scripts https://docs.microsoft.com/archive/blogs/nelson_araujo/automating-vsdm-via-scripts Wed, 18 Jan 2006 15:39:00 GMT https://blogs.msdn.microsoft.com/nelson_araujo/2006/01/18/automating-vsdm-via-scripts/ Sample scripts are bundled with VSDM in its installation folder (by default C:\Program Files\VSDM\samples). It is recommended that you have some understanding of the VSDM solution before continuing to read this article.

Option Explicit
Dim server
Dim wsh
Dim inet
Dim newVM
Dim vmName
Dim template
Dim network
Dim vmID
Dim rand

' This variable points to your VSDM server root
' e.g.: https://yourserver:81
server = "https://myserver"

' These variables define your VM name and template used
vmName = "AutomationTest" ' Your machine name
template = "xp-pro" ' Machine template to base on
network = 2 ' 2 = Internal Network (but subject to change)

' Random number to avoid collision when running this sample
rand = Now
rand = Replace(rand, "/", "-")
rand = Replace(rand, ":", "-")

Set wsh = CreateObject("WScript.Shell")
Set inet = CreateObject("InternetExplorer.Application")

' Building your VM name
vmID = wsh.ExpandEnvironmentStrings("%USERNAME%." & template & "." & vmName & " " & rand)

' URL to create a new VM
newVM = server & "/vm_ctrl.asp?action=add&name=" & vmID &_
   "&template=" & template &_
   "&types=" & template &_
   "&nettype=" & network

'WScript.Echo "Create <[" & newVM & "]>"

' Call the Internet object to perform the action
WScript.Echo "Performing action. Please wait..."
inet.Navigate newVM

' Wait the request to complete
while inet.Busy
   WScript.Echo "Waiting to complete..."
   WScript.Sleep 1000
wend

WScript.Echo "Request completed"

]]> Security: What to configure when using VSDM? https://docs.microsoft.com/archive/blogs/nelson_araujo/security-what-to-configure-when-using-vsdm Thu, 22 Dec 2005 17:51:00 GMT https://blogs.msdn.microsoft.com/nelson_araujo/2005/12/22/security-what-to-configure-when-using-vsdm/ Q: What do I need to configure on Virtual Server or File System to secure my installation?

A: Nothing!

If you are using VSDM to manage your Virtual Server, whenever you apply the Security Policy VSDM automatically hardens Virtual Server and File System for you. Just make sure your <Security> section (or in the Wizard: Users, Teams, Guests) are correct.

Whenever you change these settings, VSDM will popup a request for you to apply the policy again. Just click the Apply button and you are good to go.

]]> Error "FATAL: Cannot load config file" https://docs.microsoft.com/archive/blogs/nelson_araujo/error-fatal-cannot-load-config-file Thu, 22 Dec 2005 17:42:00 GMT https://blogs.msdn.microsoft.com/nelson_araujo/2005/12/22/error-fatal-cannot-load-config-file/ If you just installed VSDM and when you create a virtual machine you continuously get this error message, you might be missing some configuration information. To resolve this issue, follow the steps below:

  • Make sure you log in as administrator
  • Select "Administration" page on VSDM main page

Tip #1: If you cannot open the page and you get access denied, please review the Security settings of the vsdm_config.xml file or go back to the Wizard and check the settings.

  • Look at the "System Dashboard" and make sure all the items show a green check
  • If you have any missing configuration, warning messages will show there. Please act on all of them (usually a "one click" resolve button is provided)

Done, you might be good to start using VSDM.

Tip #2: If your machine is not joined to a domain, only local accounts can be authorized by Windows, even if you come from a domain-joined computer. In this case, please use the computer name as the Domain for the administrator account.

Tip #2.1: You might create local accounts that match the same username and password on the domain and authorize those. Windows will automatically enable them if you are using Internet Explorer 4.0 or greater.

]]> Why my VM does not start? https://docs.microsoft.com/archive/blogs/nelson_araujo/why-my-vm-does-not-start Fri, 19 Aug 2005 01:07:00 GMT https://blogs.msdn.microsoft.com/nelson_araujo/2005/08/19/why-my-vm-does-not-start/ In my previous post I talked about the need to keep the template ID and VM names small. If you make them too big, your machine might not start. You can check the Virtual Server Web Administration page to make sure this is the reason (Administration > Launch)

You might also inspect your default VMs folder on vsdm_config.xml file. All those ingridients are mixed together and if one or more are too big, it might overflow the OS limit.

Fix: Try to reduce the template ID, machine names and/or folder locations to smaller lengths.

]]> Hint: Keep you Template ID small https://docs.microsoft.com/archive/blogs/nelson_araujo/hint-keep-you-template-id-small Fri, 19 Aug 2005 01:04:00 GMT https://blogs.msdn.microsoft.com/nelson_araujo/2005/08/19/hint-keep-you-template-id-small/ A very useful hint for the VSDM administrators: keep the template IDs as small as possible. The Template ID will be used to build the Virtual Machine name, virtual machine folder and other important system information.

The operating system has a maximum file and path names and making either the template ID or the VM name too big (or both) might lead the system to fail to start the VM.

If possible also avoid using spaces or other "funny" characters on it. Dots (".") are definitely prohibited to be used as part of the template ID.

]]>