Search results for 'app:weblogs' matching tag 'Windows Server'

Another reference on installing Windows 8 on VHD(Boot from VHD)

Richard — Mon, 20 Aug 2012 05:00:00 GMT

Just found another article talking about it, please reference here:

http://blogs.technet.com/b/haroldwong/archive/2012/08/18/how-to-create-windows-8-vhd-for-boot-to-vhd-using-simple-easy-to-follow-steps.aspx

Copy from there(I hope Harold don't mind my re-post):
==============

I have placed the imagex.exe and some VHDs that I have created (in case you don’t want to create your own) in my drop box folder so feel free to grab them.

http://aka.ms/hwitcampfiles

In order to perform the steps in my blog, there are a couple of things that you will need to have access to – all of which are free. I will use a deployment utility called ImageX.exe from the Windows Automated Installation kit (WAIK). Also, you will need to have some way to either mount an ISO image or have the DVD or thumb drive with the Windows 8 installation media on it. I happen to use a freeware tool called Magic ISO CD/DVD Manager to mount ISO images.

Before I provide the detailed steps, let me just provide an overview of the process.

First, I need to be running Windows 7 or higher or Windows Server 2008 R2 or higher in order to perform these steps and have administrative access.
I then need to create a VHD file and format it.
Mount the ISO of Windows 8 (or have the thumb drive or DVD inserted or just have the source files available).
Open a Command Prompt (run as Administrator).
Use ImageX to “install” Windows 8 into the VHD.
Add the installation of Windows 8 to the boot menu.

Now, for the details behind the above 6 steps. I will be providing screen shots of this process from a Windows 7 machine.

Create and mount VHD

To create and mount the VHD, I will use the Computer Management console to access Disk Management. I can start this by running it from the Administrative Tools Group or right click on Computer and choose Manage.
Once Computer Management console opens, I will click on Disk Management on left pane and wait for the list of drives to refresh. Once the list of drives appear in the middle pane, I will right click Disk Management and select Create VHD.
The Create and Attach VHD Wizard appears. I have to provide a name of the VHD file that I want to create (specify directory location), size and type (dynamic or fixed). You can specify the size and type that meets your needs, but keep in mind that the size of the partition you set is important as you will need that much actual free disk space in order to boot to that VHD. Also the type determines how much disk space will always be in use. Since I use laptops for most of my work and I don’t have 1 TB laptop drives, I try to keep the size of all my VHDs that I use for multi-boot purposes to a minimal size. I find that 20 GB partitions is plenty and that dynamically expanding work just fine for my purposes.
Once I click OK, the new VHD file is created and automatically mounted and visible in Disk Management. From there I right click Disk 2 and select Initialize to Initialize the disk as MBR. After the disk is initialized, I create and format a simple volume.
After the disk has been formatted, Windows 7 automatically assigns a drive letter to the volume (in my example, it is F:). I have also mounted the ISO of Windows 8 Enterprise 90 Day Eval and it is available as drive E: in my example.
I then start a command prompt running as Administrator and go to the directory in which my ImageX.exe is located (makes it simple and in my case it is C:\Source).
In the command prompt, I issue the following command:
imagex /apply e:\sources\install.wim 1 f:\

I am essentially installing Windows 8 from the install.wim file located in the sources directory of the source files and selecting the 1st OS instance in the WIM file and installing it to drive F:\ (VHD file)
Once the process completes, I can dismount the VHD and save a copy off for future use or immediately add it to the boot menu. To dismount the VHD, go to Disk Management and right click Disk 2 and select Detach VHD.
Once I make a backup copy of the VHD file for future use, I will go ahead and Mount the VHD again to add that installation to the boot menu. To do this, I will right click Disk Management and select Attach VHD. The Attach VHD Wizard will start. I can either browse to the VHD or just type it in the Location field.
The VHD will be mounted and will be assigned a drive letter by the system. In my case, it is drive F: again.
Go back to the Administrative Command Prompt and type the following command to add the installation to the Boot Menu:

bcdboot F:\windows
Once the command finishes, you will now have the new Windows 8 entry in your boot menu.

The first time you boot to this installation, Windows 8 will detect your devices and install the appropriate drives and then reboot. Upon reboot, you will configure the computer name and a user account like you normally would on a new Windows 8 installation.

If you no longer want to have this option in your boot menu, use MSCONFIG (boot tab) to delete the unwanted entry.

Hopefully, this simple and easy to follow guide will help you to successfully create and boot to your own installations of Windows 8 (or Windows Server 2012).

=====================

Will Dispersal Replace RAID?

Richard — Mon, 20 Aug 2012 05:00:00 GMT

A good article on it:

http://wikibon.org/wiki/v/Is_RAID_Obsolete%3F

From the article:

For the foreseeable future dispersal will not be focused on transactional database environments, where RAID will continue to perform well and be combined with flash, for example. In these instances, multiple copies are warranted as data sets are smaller and of higher value. Dispersal will fit well with large scale applications such as social networks, medical images, certain government applications, archiving, intelligence applications and the like where storage will reach into the tens of petabytes in capacity.

Windows Server Failover Cluster 2012 in Depth

TBittner — Tue, 24 Jul 2012 05:00:00 GMT

Find here all sessions from Tech-Ed which covers all details about Windows Server Failover Cluster 2012. Every session takes about one hour. But it is worth taking time watching all of the sessions.

Virtual Machine do not start on Hyper-V when using AMD CPU

Richard — Sat, 14 Jul 2012 05:00:00 GMT

My student got a problem on running VM on a AMD FX CPU machine. You may reference this to solve the problem:

Virtual machine does not start on a computer that has an AMD CPU that supports the AVX feature and that is running Windows Server 2008 R2
http://support.microsoft.com/kb/2568088

Clear all the remote desktop session remotely

Richard — Mon, 09 Jul 2012 05:00:00 GMT

My best friend just asked is it possilbe to killing remote desktop session remotely. The reason for doing that was cause by my friend need to physically go back to his office and logon to the server in order to clear the connection in last weekend.
For me, i will try "mstsc.exe /console" to try to remote control the console of that server and disconnect all the other remote session first.
However, if this don't work, after some research....I found the following methods:

Method 1:

Open CMD with admin right, then ---

A. Type "qwinsta /server:xxx.xxx.xxx.xxx" into the window, replacing "xxx.xxx.xxx.xxx" with the IP address of your server. When you hit "Enter," a list of active remote-desktop connections will appear. Each session will have an ID number assigned to it.

B. Use the "rwinsta /server:xxx.xxx.xxx.xxx id" command, replacing "xxx.xxx.xxx.xxx" with the IP address of your server and "id" with the ID number of the session you want to end. When you hit "Enter," Windows will end the selected session.

Method 2:

A. Go to CMD prompt and run "quser /server:YOUR_SERVER_NAME", it will list all the remote connection.

B. Still in CMD prompt, run "logoff rdp-tcp#123 /server:YOUR_SERVER_NAME"(where 123 is the sessionname)

“speaking 2.0” at Microsoft TechEd today

UlfBSimon-Weidner — Thu, 14 Jun 2012 05:00:00 GMT

I’m speaking today about “The Evolution of Active Directory Recovery” at TechEd 2012 US (SIA319, 1pm in Hall N310). The session will also be streamed.

I had a great idea, and I’m looking forward to see how it’s working. And I haven’t seen this before :

I’ll be taking questions using Twitter.

If you are in the audience (in the hall or online) and you have any questions, just twitter them using the hashtag #TESIA319 – this enables me to follow up with the answers either in the session, or if we are short on time or have to many sessions I’m following up afterwards. This also enables attendees who are not sitting close to a Microphone, who are watching the streamed version or who feel more comfortable writing than speaking to ask their questions.

Two simple rules: use the #TESIA319 hashtag – I will not monitor anything else during the session, and please ask questions in the areas I’ve covered, so that we can try avoiding to have questions which are covered in the next slides.

Looking forward to the session and hopefully seeing you there!

Ulf B. Simon-Weidner

Erro NFe: (Causa provável: a cadeia de certificação do Web Service acessado ou do certificado cliente inexistente no repositório de certificados do usuário corrente do Windows

paleo — Fri, 01 Jun 2012 05:00:00 GMT

Com o início da utilização da Nova Cadeia de Certificados da NF-e, muitos sistemas passaram a apresentar problemas. Por que isso ocorre?

Em um computador baseado no Windows Server 2003 ou Windows XP, não é possível obter certificados de uma autoridade de certificação baseada no Windows Server 2008 (CA). Esse problema ocorre se a autoridade de certificação estiver configurada para usar criptografia SHA2 256 ou criptografia superior (384 SHA2 ou SHA2 512).

Como resolver? Basta instalar o KB 968730: http://support.microsoft.com/kb/968730

Hyper-V in Windows Server 2012

Richard — Thu, 03 May 2012 05:00:00 GMT

A useful document blog post which talk about the virtualization in Hyper-V 3 in Windows Server 2012!

http://blogs.technet.com/b/windowsserver/archive/2012/04/05/windows-server-8-beta-hyper-v-amp-scale-up-virtual-machines-part-1.aspx

Ref: Windows Server “8” Beta: Hyper-V & Scale-up Virtual Machines Part 1…

Richard — Wed, 18 Apr 2012 05:00:00 GMT

A good reference on the coming Hyper-V V3:

http://blogs.technet.com/b/windowsserver/archive/2012/04/05/windows-server-8-beta-hyper-v-amp-scale-up-virtual-machines-part-1.aspx

It also talk about NUMA.

Erro no NOD 32: "Error communicating with kernel"

paleo — Mon, 09 Apr 2012 05:00:00 GMT

Esta semana já vi três casos onde o NOD32 apresentava a mensagem de erro: "Error communicating with kernel"

Como resolver? Muito simples!

Nos três casos o problema era o mesmo. O serviço do NOD32 estava parado após a instalação de uma atualização do Windows e bastava reiniciá-lo manualmente.

Os procedimentos para isto são:

Clique em Iniciar;
Clique em Executar;
Digite services.msc;
Localize o serviço ESET Service;
Clique em Start;
Pronto!

Caso isso ainda não resolva o seu problema, sua máquina provavelmente tenha sido infectada durante o período em que o antivirus estava parado e o mais provável é que você esteja infectado com o Win32/Sirefef (Zero.Access rootkit).

Para removê-lo execute os passos descritos em: http://kb.eset.com/esetkb/index?page=content&id=SOLN2895

Se não era ele, ainda pode ser o Win32/IRCBot.ANR. Neste caso faça uma limpeza via linha de comando, conforme descrito em: http://kb.eset.com/esetkb/index?page=content&id=SOLN2903