Exemplo 1

New-VHD -Path c:\Base.vhdx -SizeBytes 10GB

Neste exemplo será criado um disco virtual DINÂMICO no formato VHDX de 10GB na unidade C:

Observações:

Exemplo 2

New-VHD -ParentPath c:\Base.vhdx -Path c:\Diff.vhdx –Differencing

Neste exemplo será criado um disco virtual DIFERENCIAL no formato VHDX ,como o nome Diff.vhx  usando como disco pai o disco Base.vhdx

Observações:

• Esse tipo requer uma pequena quantidade de armazenamento físico quando ele é criado e requer mais armazenamento conforme o tamanho do disco cresce. O tamanho máximo de um disco diferencial é restrito pelo tamanho máximo do seu disco rígido pai.
• Bloqueie ou proteja o disco pai contra gravação antes de usar o disco diferencial. Caso contrário, se o disco pai for modificado por outros processos, qualquer disco diferencial relacionado a ele se tornará inválido e todos os dados gravados serão perdidos.

Exemplo 3

New-VHD -Path C:\fixed.vhd -Fixed -SourceDisk 2 -SizeBytes 1TB

Este exemplo cria um disco fixo de  1 TB em formato VHD no caminho especificado.

Observações:

• Os dados para o disco rígido virtual é preenchido a partir de outro disco identificado pelo sistema pelo numero 2.
• Você pode listar os discos conectados ao sistema e ao número associado a cada disco usando o comando Get-Disk

Exemplo 4

New-VHD -Path c:\LargeSectorBlockSize.vhdx -BlockSizeBytes 128MB -LogicalSectorSize 4KB -SizeBytes 1TB

Neste exemplo será criado um disco DINÂMICO de 1 TB com blocos de 128MB e setores de 4KB

• Gerenciar o tamanho de setores e blocos só é possível em discos no formato VHDX no formato VHD não é possível, estes valores assumirão os valores padrão.

Créditos: http://blog.astreinamentos.com.br/2013/04/gerenciando-maquinas-virtuais-no-hyper.html

I recently experimented with Hyper-V 2012 and found there was no easy way to disable complex passwords, so after searching the net for a while I came across a nice solution that didn’t involve joining and leaving domains and interfering with group policy.  Here it is –
First step is to insert a USB stick and check which drive letter it is (D: in my case), then we can export our current policy:

secedit /export /cfg D:\new.cfg

Remove the USB stick and edit the file on another PC.  We are interested in PasswordComplexityvalue within the [System Access] section.

[System Access]
MinimumPasswordAge = 0
MaximumPasswordAge = 39
MinimumPasswordLength = 0
PasswordComplexity = 1
PasswordHistorySize = 0
...

Value should be changed to 0 in order to disable complexity check.

Save the file back, insert it back in to the Hyper-V server and import the configuration:

secedit /configure /db C:\Windows\security\new.sdb /cfg D:\new.cfg /areas SECURITYPOLICY

You can now add users with out complex passwords.

Créditos:http://sion-it.co.uk/tech/windows/disable-complex-password-requirement-on-hyper-v-server-2012/

Find all computers on the current domain with a name that starts with “wks” :

C:\> dsquery computer -name wks* -desc desktop*

Find all computers in the Aberdeen OU:

C:\> dsquery computer ou=Aberdeen,ou=Workstations,dc=ss64,dc=com

Echo all inactive computer accounts (more than 4 weeks inactive):

C:\> dsquery computer -inactive 4

Disable all inactive computer accounts (more than 4 weeks inactive):

C:\> dsquery computer -inactive 4 | dsmod computer -disabled yes

Créditos: http://ss64.com/nt/dsquery-computer.html

Installing a RDP SSL Certificate

1. On your Microsoft certificate authority server open the Certificate Templates console.

2. Duplicate the Computer template and use the Windows Server 2003 Enterprise format (Server 2008 v3 templates will NOT work).

3. Change the template display name to RemoteDesktopComputer (no spaces). Verify the Template Name is exactly the same (no spaces). You can use a different name if you want, but both fields must match exactly.

4. Now we need to create an application policy to limit the usage to RDS authentication, then remove the other application uses for the certificate. On the extensions tab click on Application Policies then click on Edit.

5. Click on Add, then click on New.  Set the value of Name to Remote Desktop Authentication. Change the object identifier to 1.3.6.1.4.1.311.54.1.2.

13. In the same GPO node, configure the Require use of specific security layer for remote (RDP) connections to use SSL (TLS 1.0).

14. Wait for the GPO to replicate, then refresh the GPO on a test server. Wait a minute, then open the Certificates MMC snap-in for the computer account. Look in the PersonalCertificates store for a certificate that has the Intended Purposes of Remote Desktop Authentication. If it’s not there, wait a minute, and refresh. If it never appears, something is wrong. Look at the gpresult to make sure your GPO is being applied to the server.

15. Once the certificate appears, double click on the certificate to open it. On the Details tab look at the first few characters of the thumbprint value and remember them.

16. To make sure the RDP service is aware of the new certificate, I restart the Remote Desktop Services service.

17. Open an elevated PowerShell prompt and run this command:

Get-WmiObject -class “Win32_TSGeneralSetting” -Namespace root\cimv2\terminalservices -Filter “TerminalName=’RDP-tcp’”

Validate that the Security Layer value is 2 and that the thumbprint matches the certificate. If both of those settings are correct, then you are good to go!

As a quick test I attempted to connect to this server from a non-domain joined computer that did not have the root certificate for my CA. I configured the RDP client to warn on any security issues. As expected, the client threw errors about the CRL not being available, and that it didn’t trust the chain. I also viewed the certificate and verified it was the correct one.

It seems Windows 8 has much more stringent certificate checking than Windows 7. The screenshots below are from Windows 7, in case you didn’t recognize the chrome. When using a Windows 7 non-domain joined computer to access the same TLS protected server, I got NO certificate warnings. That was even with the RDP 8 add-on hotfix. I’m glad to see Win8 does thorough certificate validation.

Connecting to the same server from a domain-joined computer that trusted the root CA resulted in no security warnings and a successful connection. If you look at a Wireshark capture you can also validate that CRL information is being exchanged between the computers, which means TLS is being used.

Créditos: http://www.derekseaman.com/2013/01/creating-custom-remote-desktop-services.html

Dsquery is a command-line tool that is built into Windows Server 2008. 
It is available if you have the Active Directory Domain Services (AD DS) server role installed. 
To use dsquery, you must run the dsquery command from an elevated command prompt. 
To open an elevated command prompt, click Start, right-click Command Prompt, and then click Run as administrator.

To find inactive computer accounts (number is inactivity in weeks):
dsquery computer -inactive 2

To find computers with stale passwords (number is stale in days)
dsquery computer -stalepwd 45

There is also a combination to disable / delete the accounts:
combined with dsmod/dsrm

dsquery computer -inactive 4 | dsmod computer -disabled yes
dsquery computer -stalepwd 45 | dsrm computer

You can get additional info on both of these tools with dsquery computer /? ,dsmod computer /?, and dsrm computer /?

Créditos: http://community.spiceworks.com/scripts/show/339-find-and-or-cleanup-old-computer-accounts-in-ad