Start Windows PowerShell. Right-click the Windows PowerShell icon on the taskbar, and then click Run as Administrator.
Run the following Windows PowerShell commands:
PS C:\> Import-Module ServerManager
PS C:\> Add-WindowsFeature -name FS-Data-Deduplication
PS C:\> Import-Module Deduplication
PS C:\> Enable-DedupVolume E: & Enable-DedupVolume D:
And wait….
Saving already 240GB on my home lab…. Dedub is great
Today I was moving my testlab enterprise root CA from a Windows 2008 r2 server to a new Windows 2012 with a different server name. To accomplish this, I used this excellent Technet Post . I encountered no problems!
Before beginning these steps, ensure that:
You have setup a Microsoft account in Windows 8.
You have your Active Directory (AD) username and password. Your username is usually the first part of your UCSD email address (before the @ symbol). If you forgot your password, you can reset it.
You have an Exchange account in the UCSD Campus Exchange Organization.
Click the Mail tile in the Start screen to open the Mail program
Press Windows key + I on the keyboard to open Mail settings
Select Accounts
Enter your e-mail address in the Email address field
Enter your AD passsword in the Password field
Select Show more details
Enter <yourservername> in the Server address field
Enter <yourdomain> in the Domain field
Enter your AD username in the Username field
Click Connect to add the account
Features on Demand
“Features on Demand (FoD)” is a new concept in Windows 8 that allows administrators and image builders to reduce the amount of space. .
When you install an application that’s ask for .Net Framework 3.5 that will be automatically installed. You don’t have to deploy it automatically with it…
In Windows 8, .Net Framework 3.5 is now a Feature on Demand. And to simplify the installation of common legacy versions of the .Net Framework, .Net 3.0 and 2.0 have been included in the same feature package as 3.5. That means if any of those three versions need to be installed, all the administrator needs to do is enable the single .Net Framework 3.5 feature in Windows 8.
Installation Sources
The .Net Framework 3.5 payload can be obtained from any of the following sources:
· Windows Update (WU)
· A Windows Image file (.wim) to which the payload has been added
· The \sources\sxs folder on the installation media
There are unique advantages to using each. The source can be specified for the environment using a new Group Policy setting. It can also be specified when installing .Net 3.5 manually on an individual machine or image.
The simplest scenario is one in which WU is accessible to both the machine and the user, and the machine is not configured to obtain updates from Windows Server Update Services (WSUS). In this case, when the feature is enabled, the user will be prompted for permission to download the update. If permitted, Windows will download the payload directly from Windows Update and install the feature. Done!
In more controlled environments, administrators might want to redirect such download requests to an alternate source such as a Windows Image file (.wim) to which the payload was added, or the\sources\sxs folder from the installation media. There might also be network , proxy, or security configurations that prevent users from directly accessing Windows Update. Additionally, WSUS does not currently support the payloads for Features on Demand, although it does support the subsequent patching of the features. So in environments where machines are configured to obtain updates from WSUS, administrators will need to configure the source for initial FoD installations.
To allow administrators to manage these scenarios, a new Group Policy setting was introduced in Windows 8 / Windows Server 2012: “Specify settings for optional component installation and component repair”, located under Computer Configuration\Administrative Templates\System:
This policy allows the administrator to configure the installation of Features on Demand and feature store repair operations to use only authorized locations.
When this policy is enabled, a network location (for example, a file server) can be specified for both repair of the feature store, and enabling features whose payloads were not originally added. The Alternate source file path can point to a \sources\sxs folder or a Windows image (WIM) file using the WIM: prefix. The repair WIM can be different than the initial WIM file used for installation. You can specify multiple paths by using “;” between the paths. Valid syntax is “wim:<path to wim>:<index>”. Or “<path to sxs folder>”.
Examples:
\\server\Win8Media\sources\sxs
wim:\\server\sourcewim\install.wim:3
If you select Never attempt to download payload from Windows Update, WU is not contacted during an installation or repair operation.
If you select Contact Windows Update directly to download repair content instead of Windows Server Update Services (WSUS), attempts to add features (for example, .NET Framework 3.5) or repair the feature file store use Windows Update to download files. Target computers require Internet and WU access for this option. Normal servicing operations continue to use WSUS if it has been configured as a source.
Install Server 2012. Join Server to your Domain.
Select Behind an Edge Device
Public name voor mij is dat is: thuis.wardvissers.nl
Remote Access Review & Next
View Remote Access Review
Finish
Overview
Policy’s
Windows 8 Client
I have a Firewall/NAT router. So you need open some ports
DirectAccess works great. Every where I work I have access to my docs & email.
Create a folder to mount a Windows Imaging File (WIM) in with the command mkdir c:\mountdir
Determine the index number for a Server with a GUI image (for example, SERVERDATACENTER, not SERVERDATACENTERCORE) using this command at an elevated command prompt: Dism /get-wiminfo /wimfile:<drive>:sources\install.wim
Mount the WIM file using this command at an elevated command prompt: Dism /mount-wim /WimFile:<drive>:\sources\install.wim /Index:<#_from_step_2> /MountDir:c:\mountdir /readonly
Start Windows PowerShell and run this cmdlet:
Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell –Restart –Source c:\mountdir\windows\winsxs
Alternatively, if you want to use Windows Update as the source instead of a WIM file, use this Windows PowerShell cmdlet:
Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell –Restart
To convert to a Server Core installation with Windows PowerShell: run the following cmdlet: Uninstall-WindowsFeature Server-Gui-Mgmt-Infra -restart
The Hands-on Guide: Understanding Hyper-V in Windows Server 2012 gives you simple step-by-step instructions to help you perform Hyper-V-related tasks like a seasoned expert.
You will learn how to:
Download the first 5 chapters (180 Pages) today! Klik on the Picture to go to the Veeam Website
In Windows 8 there is a movie that is played for the first time logon and there is a Group Policy setting you can use to disable it. Mikael Nystrom writed a nice MDT Application you can download and install and put it into your task sequence for Windows 8 and you will never ever see it once more. Happy deployment!
Download the zip file, extract it and create a new Application in MDT 2012 Update 1.
Select Application with Source Files
Edit Task Sequence
VMWare released a preview of the VMware View Client for Windows Store. This Windows Store client will run in the tiled view of Windows RT and Windows 8.
As this is a preview, it does have a number of limitations:
The Windows Store client has additional requirements for server certificate checking:
We are excited to release this Windows Store client and look forward to improving it in subsequent releases. To install the client, go to the store from your Windows 8 system and search on VMware.
The existing VMware View Client for Windows (version 5.2 or later) runs in Windows 8 desktop mode. If you are running Windows 8 (not Windows RT) VMware recommends that you use our existing VMware View Client for Windows in the Windows 8 desktop mode for maximum functionality