Mike wrote: 

“I’ve found an even easier way to do this.  I found a PowerShell Hyper-V script at:

http://www.codeplex.com/PSHyperv

It has a lot of functions already, and I added a “Kill-VM” function that automates the kill process:

Kill-VM <VM name>

My modified script is attached to this message.

To use it, you need to install PowerShell (Under Server Manager -> Features in Win2008).  Once installed, run PowerShell from Start -> Search, find the script, and type:

. .\hyperv.ps1

Once loaded into memory, type:

Kill-VM <VM Name>

Enjoy”

Click here to download script - hyperv-script.zip

http://www.thewebsiteisdown.com/salesguy.html

For now the only solution I found is to use command:

shutdown -p now

and when it turns off I turn it back on with Hyper-V console…

 :) hope it helps

- download FreeBSD ISO image from:
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200806
Download this ISO image:
7.0-STABLE-200806-i386-disc1.iso

- create new Virtual Machine using Hyper-V
- remove default network card that is added by wizard
- add hardware and chose Legacy network adapter
- start the machine and “mount” ISO image to start booting FreeBSD…
- install it with parameters you want…

- **** NETWORK PROBLEMS **** Even if you are runing DHCP server on your network your FreeBSD machine will not get IP from your DHCP server (my machine did not) so I used ifconfig to add IP and gateway this way:

ifconfig de0 10.70.60.201 - this is IP in my subnet you should use one of your free IP’s
ifconfig de0 down
ifconfig de0 up

You can now chec status of your IP with:
ifconfig

Ok, now we need a gateway to get to the internet:
route add 0.0.0.0 10.70.60.1 This will add your default gateway (for example my gateway is 10.70.60.1)…

try to ping an public IP address to see it is working… As you can see in my screenshots it works for me.

FreeBSD on Hyper-V [docx]
FreeBSD on Hyper-V [pdf]

*** There is still one problem unsolved for now… If you try to reboot Free BSD, Hyper-V does not Turn off the machine … I am trying to solve that with some Nejc tricks

If you you need network connectivity imediatly after installation you can first use Legacy network adapter and after Integration services intallation you can replace it with Network adapter that was configurated during creation of Virtual Machine.

Integration services will also solve your unknown devices in device manager.

You install Integration services by clicking on Action / Insert Integration Services Setup Disk when you are logged on your virtual machine.

If you did not select any network adapters to be used by Hyper-V during Hyper-V installation you can see your physical two adapters in Network connections.
After you run Virtual network manager and you create new network for example “External network” that is connected to your second physical card your physical card lose connectivity and all protocols and services are unchecked except Microsoft Virtual Network Switch Protocol (and HP Network configuration utility - but this is specific to my case becouse I use HP server). When you finish the wizard you can see that in your Network connections there is another adapter called “External network” - it is now used for your Virtual machines.

HINT! Do not do that remotely if you are not completely shure which adapter is which… If you make a mistake you will need physical access to the machine to change network parameters.

Example:
Hyper-V virtual network manager example [docx]
Hyper-V virtual network manager example [pdf]

This Step-By-Step have some specific information regarding installing Hyper-V on HP DL380 server which I have at home - so I have explained how to enable virtualization in BIOS (it may vary from bios to bios) and some specific problem HP servers with HP Network configuration utility have when you try to install Hyper-V (server hangs on “Configuring Updates Stage 3 of 3″ on 54% or 75%).

Step-by-step installing Hyper-V final version [docx]
Step-by-step installing Hyper-V final version [pdf]

Additional resources:
http://www.microsoft.com/windowsserver2008/en/us/virtualization-consolidation.aspx - Microsoft Virtualization
http://blogs.technet.com/virtualization/ - Microsoft Virtualization blog
http://www.microsoft.com/downloads/details.aspx?FamilyId=F3AB3D4B-63C8-4424-A738-BADED34D24ED&displaylang=en - Hyper-V Final version update
http://support.microsoft.com/default.aspx/kb/950792 - HP servers problem when installing Hyper-V

 Great stuff!!!

You can solve this problem by using “Shrink” command in the MS SQL Server Management Studio Express

First you need to connect to your Sharepoint 3.0 database called: \\.\pipe\mssql$microsoft##ssee\sql\query - just put this string in your “Server name” field:

\\.\pipe\mssql$microsoft##ssee\sql\query

 Create full backup of all databases before continuing!

After that we should change restore mode from “Full” (this the parameter that allows .log.ldf to grow that large as transaction logs are not purged) to “Simple”:

Expand Databases, right mouse click on Sharepoint_Config… Properties, Options, Recovery model: Simple and click OK

Shrink the database procedure:

Expand Databases, right mouse click on Sharepoint_Config… Tasks, Shrink, Files in File type select Log and click OK
Your log file will become radicaly smaller.

Be sure you backup your databases before this procedure and also on daily bases…

Good luck!

 Also check:
http://geekswithblogs.net/RogueCoder/archive/2008/06/03/122588.aspx
http://www.karaszi.com/SQLServer/info_dont_shrink.asp

 Here is my presentation…

 Tutti frutti security - 5 security tricks ppt / pptx