After increasing a virtual machine VMDK size you need to also resize this partition in Windows.
This can be completed remotely using PowerShell. There are various methods to run this but I prefer to use “Server Management” and admin the machines from here. you can run “PowerShell” on a remote session to run the script below.
This process will increase the C:\ partition to use all space that has been allocated by VMware. (Replace -DriveLetter with the required drive)
There are various method
$size = Get-PartitionSupportedSize -DriveLetter C
Resize-Partition -DriveLetter C -Size $size.SizeMax -Verbose
Write-Output "Drive Extension Complete!"
I’ve been having some problems trying to enable UAC and spent some time trying to resolve this, starting a technet post to help. My preference would be to use Group Policy (GPO) to enable this, however experienced issues with the UAC not being fully functional (no admin elevation prompts). Unfortunately I never really got to the bottom of the issue., however as a workaround used the following script in a *.bat file to disable it in the registry.
Enable UAC (via *.bat)
%windir%\System32\reg.exe ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v EnableLUA /t REG_DWORD /d 1 /f
Disable UAC (via *.bat)
%windir%\System32\reg.exe ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v EnableLUA /t REG_DWORD /d 0 /f
Problems with GPO (technet): Enable UAC via GPO | Windows 7
Well it is a New Year! But not sure how “Happy” it is so far… 🙂
Back to work and with more technical conundrums! Lets hope there isn’t too many Bugs, Viruses and Windows updates to bring everything crashing to the ground on a cold, wet server room floor!
Best Wishes to all the I.T. community in 2013!
DNS Server running on a Windows Server 2008 offers many new functionality.
One of them is Global Name Zone or GNZ.
GNZ gives a chance for organisations to move to a DNS-only environment by
eliminating the need to have a WINS Server on the network.
Make sure that the Remote Desktop Users group has sufficient permissions to log on through Terminal Services.
- Click Start, click Run, type secpol.msc, and then click OK.
- Expand Local Policies, and then click User Rights Assignment.
- In the right pane, double-click Allow logon through Terminal Services. Make sure that the Remote Desktop Users group is listed.
- Click OK.
- In the right pane, double-click Deny logon through Terminal Services. Make sure that the Remote Desktop Users group is not listed, and then click OK.
- Close the Local Security Settings snap-in.
Make sure the user is added to the Remote Desktop Users group:
- Open Computer Management.
- In the console tree, click the Local Users and Groups node.
- In the details pane, double-click the Groups folder.
- Double-click Remote Desktop Users, and then click Add….
- On the Select Users dialog box, click Locations… to specify the search location.
- Click Object Types… to specify the types of objects you want to search for.
- Type the name you want to add in the Enter the object names to select (examples): box.
- Click Check Names.
- When the name is located, click OK.
Check the users or groups to Terminal Services RDP permissions:
- Open Terminal Services Configuration.
- In the Connections folder, right-click RDP-TCP.
- Click Properties.
- On the Permissions tab, click Add, and then add the desired users and =