Category: Microsoft

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.

Windows Server 2012: Convert server Core to server with a Gui

  1. Create a folder to mount a Windows Imaging File (WIM) in with the command mkdir c:\mountdir

  2. 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

  3. 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

  4. Start Windows PowerShell and run this cmdlet:

    Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell –Restart –Source c:\mountdir\windows\winsxs

  5. 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

Windows Server 2012: Convert a server with a Gui to Core with Windows PowerShell

To convert to a Server Core installation with Windows PowerShell: run the following cmdlet:
Uninstall-WindowsFeature Server-Gui-Mgmt-Infra -restart

Forefront TMG 2010 SP2 Rollup 3

Microsoft released Rollup 3 for Microsoft Forefront Threat Management Gateway (TMG) 2010 Service Pack 2.

For Exchange, this Rollup fixes unexpected authentication prompts when using OWA published using Forefront Threat Management Gateway (TMG) 2010 in conjunction with RSA authentication and Forms-based Authentication (2783345)

 

2700248 A server that is running Forefront Threat Management Gateway 2010 may stop accepting all new connections and may become unresponsive

2761736 All servers in a load-balanced web farm may become unavailable in Forefront Threat Management Gateway 2010

2761895 The Firewall service (WSPSRV.EXE) may crash when the firewall policy rules are reevaluated in Forefront Threat Management Gateway 2010

2780562 PPTP connections through Forefront Threat Management Gateway (TMG) 2010 may be unsuccessful when internal clients try to access a VPN server on the external network

2780594 A non-web-proxy client in a Forefront Threat Management Gateway (TMG) 2010 environment cannot open certain load-balanced websites when TMG HTTPS inspection is enabled

2783332 You cannot log on when FQDN is used and Authentication delegation is set to “Kerberos constrained delegation” in a Forefront Threat Management Gateway 2010 environment

2783339 A closed connection to a domain controller is never reestablished when Authentication delegation is set to “Kerberos constrained delegation” in a Forefront Threat Management Gateway 2010 environment

2783345 Unexpected authentication prompts while you use an OWA website that is published by using Forefront Threat Management Gateway (TMG) 2010 when RSA authentication and FBA are used

2785800 A “DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)” Stop Error may occur on a server that is running Forefront Threat Management Gateway (TMG) 2010

2790765 A “Host Not Found (11001)” error message occurs when an SSL site is accessed by using a downstream Forefront Threat Management Gateway 2010 server that has HTTPS Inspection enabled

 

For TMG, support will end on April 14th, 2015 and extended support will end on April 14th, 2020. You have some time to look into alternatives.

You can request Forefront TMG SP2 RU3 directly from support here.

Remove the Windows 8 Animation during MDT Deployment

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

image

Edit Task Sequence

image

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

MDT & SAMSUNG ATIV Smart PC Tablet Part 1

Last week i was playing with Samsung ATIV Smart PC.

Samsung ATIV Smart PC is a great device. This is one of many Touch laptops from Samsung. This Laptop is also usable as Tablet PC. Because it run Windows 8 x86 you can run al your applications on this device.

De Samsung ATIV Smart PC does not have fast Ethernet nic onboard only a Wifi NIC.

I would like to deploy our company “image” to this device.

1. Download Software Update http://www.samsung.com/us/support/owners/product/XE500T1C-A01US

2. Install Software

3. Search for XE500T1C-A01NL

4. Download al the Drivers and Software

5. Extract all Packages en sort this in Driver and Applications

6. Import the drivers in MDT

7. You need the a NIC I uses the USB 2.0 to Gigabit Ethernet NIC Network Adapter

8. Download the Driver SMSC_LAN7500.zip

9. You find after unpacking in de Windows Folder de driver LAN7500-WDF-v1.2.0.0.exe

10. You can Extract the Driver with “LAN7500-WDF-v1.2.0.0.exe /extract d:\downloads\LAN7500”

11. Import the Drivers in to same Driver Store als descripted in 6.

12. Update Deployment Share Wizard

13. Create A Task Sequence

14. Create a selection Profile descripted here: MDT 2010 Importing automatically the right driver

15. Change import driver on the Task Sequence

16. You need at Least a 4GB USB Stick

17. Format the USB stick with FAT32 How to create a bootable USB drive from an ISO image for UEFI systems

18. Mark the partition als Active
1.Open Command Prompt

2 Type: diskpart

3. At the DISKPART prompt, type: list partition

Make note of the number of the partition that you want to mark as active.

4. At the DISKPART prompt, type:

select partition n

Select the partition, n, you want to mark as active.

5. At the DISKPART prompt, type: active

19. If you’re on Windows 8, double-click your ISO image to mount it. If you’re on earlier versions of Windows, use a 3rd party utility to mount the ISO. Just search the web and you’ll find options. Or, burn the ISO to a DVD and then mount it. Once the ISO is mounted, copy all files and directories over to your newly formatted USB drive by dragging and dropping. You can also do this from the command line using robocopy or xcopy.

20. Delete the install.wim and boot.wim from the sources directory

21. Copy LiteTouchPE_x86.wim from the Boot directory on the MDT server to de Sources Map on the USB Stick

22. Rename LiteTouchPE_x86.wim to boot.wim
WP_20121221_002

23. Disable Secure Boot:
WP_20121221_001

24. Boot From USB

25. You Can deploy now your OS to your Tablet.

Part Two I will write about installing Touch Driver Software/Driver

Windows 8 – Customizing the Default Lock Screen

The update “Windows 8 and Windows Server 2012 cumulative update: November 2012” adds functionality to the Control Panel group polices that allow an administrator to designate a lock screen image on their Windows 8 and Windows 2012 computers. This setting lets you specify the default lock screen image shown when no user is signed in, and also sets the specified images as the default for all users (it replaces the inbox default image) Some restriction apply. See the Restrictions section below.
The new group policy is named “Force a specific default lock screen image” and can be found in this path in the group policy editor: “Computer Configuration\Policies\Administrative Templates\Control Panel\Personalization”

Requirements:
To deploy the new “Force a specific default lock screen image”  GP the following requirements must be met:

  1. The update “Windows 8 and Windows Server 2012 cumulative update: November 2012” must be applied to all Windows 8 and Windows Server 2012 computers that you want to deploy customer lock screen images to. This is required as the Control Panel group policy client side extension must be updated to enforce the group policy
  2. The group policy used to deploy the custom lock screen image must be edited on a machine that has been patched with “Windows 8 and Windows Server 2012 cumulative update: November 2012”

Restrictons

  • Windows 8 Enterprise or Windows Server 2012 can use the new GP “Force a specific default lock screen image” via Domain GP or via local GP
  • Windows 8 Pro can also be a target of the GP if the machine is joined to a domain

Implementation Steps for Domain Based Group Policy

  1. Patch all system with update “Windows 8 and Windows Server 2012 cumulative update: November 2012” KB 2770917
  2. Create a GPO and link it to the OU where the computer accounts are located that you want to deploy the custom lock screen image to. Alternatively you can use an existing GPO.
    a. Open the Group Policy Management Console (GPMC)
    b. Create and link a GPO to an OU or Locate an existing GPO that you want to use
  3. Create and link a GPO to an OU or Locate an existing GPO that you want to use
    a. In GPMC right click the GPO from step 2b and select edit
    b. Go this path “Computer Configuration\Policies\Administrative Templates\Control Panel\Personalization”
    c. Enable the GP “Force a specific default lock screen image”
    d. Specify the path to the image file. It is recommended to use a DFS network path to provide redundancy.
  4. After Sysvol replication has occurred and clients have refreshed their group policy settings the new lock screen will be used.

Implementation Steps for Local Group Policy

1.      Patch the system with update “Windows 8 and Windows Server 2012 cumulative update: November 2012” KB 2770917
2.      Edit Local Policy
a.       Run GPEDIT.MSC
b.      Go this path “Computer Configuration\Policies\Administrative Templates\Control Panel\Personalization”
c.       Enable the GP “Force a specific default lock screen image”
d.      Specify the path to the image file.
e.       Click OK
3.      Policy will be enforced as the next GP background refresh.

Issue with Windows Management Framework 3.0 on Exchange 2007 and Exchange 2010

Recently, Windows Update began offering the Windows Management Framework 3.0 as an Optional update. This includes all forms of update distribution, such as Microsoft Update, WSUS, System Center Configuration Manager and other mechanisms. The key bit here is that the Windows Management Framework 3.0 includes PowerShell 3.0.

Windows Management Framework 3.0 is being distributed as KB2506146 and KB2506143 (which one is offered depends on which server version you are running – 2008 Sp2 or 2008 R2 Sp1).

What does that mean to you?

Windows Management Framework 3.0 (specifically PowerShell 3.0) is not yet supported on any version of Exchange except Exchange Server 2013 (which requires it). If you install Windows Management Framework 3.0 on a server running Exchange 2007 or Exchange 2010, you will encounter problems, such as Rollups that will not install, or the Exchange Management Shell may not run properly.

We have seen rollups not installing with the following symptoms:

  • If rollup is installed through Microsoft Update, the installation might error with error code of 80070643
  • If rollup is installed from a download, the error displayed is “Setup ended prematurely because of an error.”
  • In both cases, event log might show the error with an error code of “1603”

Exchange Team adviced that Windows Management Framework 3.0 should not be deployed on servers running Exchange 2007 or Exchange 2010, or on workstations with the Exchange Management Tools for either version installed. If you have already deployed this update, it should be removed. Once the update is removed, functionality should be restored.

Translate »