Microsoft Deployment Toolkit 2013 Preview

The Client Management team is happy to announce the availability of the Microsoft Deployment Toolkit (MDT) 2013 Preview. Download the installer file and release notes from the Client Management program on Connect in the MDT group.

New members must first join the MDT group of the Client Management program on Connect.

MDT 2013 Preview includes:

  • Support for the Windows Assessment and Deployment Kit (ADK) for Windows 8.1 Preview. (The Windows ADK for Windows 8.1 Preview is available on the Microsoft Download Center.)
  • Support for deployment of Windows 8.1 Preview and Windows Server 2012 R2 Preview, as well as Windows 7 and Windows 8 families of operating systems.
  • Support for zero-touch integration (ZTI) with System Center 2012 R2 Configuration Manager Preview.

We encourage you to download and use MDT 2013 Preview, and then submit suggestions, bugs and feedback via the Connect site

ADK for Windows 8.1 Preview Available

Here is a quick summary of the changes in ADK for Windows 8.1. MDT 2013  and ConfigMgr 2012 R2 requires ADK for Windows 8.1.

Windows 8.1 Image Size (Preview)
  • Windows 8.1 Preview Code Image (x86), 2.13 GB (WIM), 7.65 GB expanded on disk.
WinPE 5.0
  • Profiling in WinPE 5.0 is removed
  • WinPE 5.0 x64 supports 4 TB of RAM (still 64 GB for x86)
  • Scratchspace set automatically to 512 MB when having more than 1 GB of RAM, otherwise 32 MB
USMT 6.3
  • Support for Windows 8.1
  • You cannot use USMT 6.3 to migrate settings from Windows XP to Windows 8.1
  • Supports Office 2013 (hotfix available for USMT 5.0).
Windows 8.1 Upgrade / Update
  • You are likely to have more free space available on the disk after upgrading Windows 8 to Windows 8.1
  • Windows 8.1 upgrade time, less than 20 minutes
Misc. Updates
  • Export compressed recovery image (/Export-Image)
  • Cleanup base components when superseded. (/StartComponentCleanup /ResetBase)

 Download

ADK for Windows 8.1.

News. Teched is coming… New version of ADK & MDT 2013

Here is a quick summary of the changes in ADK for Windows 8.1. MDT 2013 and ConfigMgr 2012 R2 requires ADK for Windows 8.1.

Windows 8.1 Image Size (Preview)

  • Windows 8.1 Preview Code Image (x86), 2.13 GB (WIM), 7.65 GB expanded on disk.

WinPE 5.0

  • Profiling in WinPE 5.0 is removed
  • WinPE 5.0 x64 supports 4 TB of RAM (still 64 GB for x86)
  • Scratchspace set automatically to 512 MB when having more than 1 GB of RAM, otherwise 32 MB

USMT 6.3

  • Support for Windows 8.1
  • You cannot use USMT 6.3 to migrate settings from Windows XP to Windows 8.1
  • Supports Office 2013 (hotfix available for USMT 5.0).

Windows 8.1 Upgrade / Update

  • You are likely to have more free space available on the disk after upgrading Windows 8 to Windows 8.1
  • Windows 8.1 upgrade time, less than 20 minutes

Misc. Updates

  • Export compressed recovery image (/Export-Image)
  • Cleanup base components when superseded. (/StartComponentCleanup /ResetBase)

Windows 7 and Windows 8 Optimization Guide for Horizon View Virtual Desktops & Antivirus Best Practices for Horizon View 5.x

VMware released two great documents!!

Windows 7 and Windows 8 Optimization Guide for Horizon View Virtual Desktops

Antivirus Best Practices for Horizon View 5.x

Error while installing WebComponents.msi

 

When configuring certificates for a lync 2010 environment, I noticed that I made a typo. Failing to correct the problem via the topology builder, I had to uninstall the lync software. After correcting my typo, the installation failed to install. This was the error I got:

image

After doing some digging I noticed also an event in the eventviewer
:image

Opening the log file as mentioned in the event, it turned out I had something to do with an duplicate entry in the applicationhost.config.

image

As stated in the error it had something to do with a duplicate entry at line 421. Opening the applicationhost.config learned that line 421 didn’t had anything to do with lync. The trick was to find OCSAuthHelperModule:

<add name=”OCSAuthHelperModule” image=”C:\Windows\Assembly\GAC_64\Microsoft.Rtc.Server.WebInfrastructure\4.0.0.0__31bf3856ad364e35\Microsoft.Rtc.Server.WebInfrastructure.dll” preCondition=”integratedMode,runtimeVersionv2.0,bitness64″ />

After deleting this entry, the installation went good!

%Windir%\System32\inetsrv\config\

Special thnx to Techsps

CreateCluster failed with 0×5 adding members to DAG in Exchange 2013

Last weekend I was building a Exchange 2013 cluster. Since everything so far was working as expected, I proceeded with creation of DAG. From EAC, creating DAG itself worked with no issues. I then went ahead and added first mailbox server to DAG. this step, however, refused to complete with error:

A server-side database availability group administrative operation failed. Error The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API ‘”CreateCluster() failed with 0×5. Error: Access is denied”‘ failed.. [Server: ward-02.wardvissers.local]

Assigning “Full Control” to Exchange Trusted Subsystem on , I assumed should fix the issue, however, it actually produced a completely different error when I tried to add the mailbox server to DAG again:

An Active Manager operation failed with a transient error. Please retry the operation. Error: The fully qualified domain name for node ‘DAG01′ could not be found.

Solution:

Pre-stage the CNO (CLUSTER NAME OBJECT)

  1. Open Active Directory Users and Computers.
  2. Expand the forest node.
  3. Right-click the organizational unit (OU) in which you want to create the new account, select New, and then select Computer.
  4. In New Object – Computer, type the computer account name for the CNO in the Computer name box. This is the name that you’ll use for the DAG. Click OK to create the account.
  5. Right-click the new computer account, and then click Disable Account. Click Yes to confirm the disable action, and then click OK.

Assign permissions to the CNO (CLUSTER NAME OBJECT)

  1. Open Active Directory Users and Computers.
  2. If Advanced Features aren’t enabled, turn them on by clicking View, and then clicking Advanced Features.
  3. Right-click the new computer account, and then click Properties.
  4. In <Computer Name> Properties, on the Security tab, click Add to add either the computer account for the first node to be added to the DAG or to add the Exchange Trusted Subsystem USG:
    • To add the Exchange Trusted Subsystem, type Exchange Trusted Subsystem in the Enter the object names to select field. Click OK to add the USG. Select the Exchange Trusted Subsystem USG and in the Permissions for Exchange Trusted Subsystem field, select Full Control in the Allow column. Click OK to save the permission settings.
    • To add the computer account for the first node to be added to the DAG, click Object Types. In the Object Types dialog box, clear the Built-in security principals, Groups, and Users check boxes. Select the Computers check box and click OK. In the Enter the object names to select field, type the name of the first Mailbox server to be added to the DAG, and then click OK. Select the first node’s computer

 Pre-Stage the Cluster Network Object for a Database Availability Group

Windows 2012 DirectAccess Quick & Dirty

Install Server 2012. Join Server to your Domain.

image

Select Behind an Edge Device
Public name voor mij is dat is: thuis.wardvissers.nl

image

Remote Access Review & Next
image
View Remote Access Review

image

Finish

image

Overview

image

image

Policy’s

image

Windows 8 Client

image

I have a Firewall/NAT router. So you need open some ports
image

 

DirectAccess works great. Every where I work I have access to my docs & email.

VMware View preview Client for Windows Store

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.

 

image

 

As this is a preview, it does have a number of limitations:

  • The client supports RDP connections but not PCoIP yet
  • No support for smart card authentication
  • To use the onscreen keyboard on a tablet, go to Settings and select Keyboard

The Windows Store client has additional requirements for server certificate checking:

  • You cannot turn off certificate verification on the client.
  • The View Connection Server or security server must have a security certificate that the client can fully verify and it must match the host name in the View Client.
  • If you plan to use a secure tunnel connection, for instance if you will be connecting remotely, the tunnel server (View Connection Server instance or security server) must also have a security certificate that the client can verify. The host name in the View Client must match the host name in the “External URL” setting shown in the Edit View Connection Server Settings dialog box, in View Administrator. For example, the field cannot have an IP address and the certificate cannot be self-signed.
  • Alternately, the user can install a self-signed certificate into the client computer, but it must be put in the local machine store rather than the current user store. The app that end users should use is called “Manage computer certificates” (certlm.msc).

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

Translate »