Category: Microsoft

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.

Update Rollup 5 version 2 for Exchange Server 2010 Service Pack 2

Update Rollup 5 version 2 for Exchange Server 2010 SP2 addresses the vulnerabilities that are described in Microsoft Security Bulletin MS12-080

http://technet.microsoft.com/en-us/security/Bulletin/MS12-080

. This update also resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:

707146 IRM-protected messages cannot be returned in search results if the messages are recorded and sent to an external contact in an Exchange Server 2010 environment’

2710975 Some MAPI property objects in an ANSI .pst file contain unreadable characters if you import the file by using the “New-MailboxImportRequest” cmdlet

2712001 ExTRA.exe does not collect data if you select a scheduled task for a data collection in an Exchange Server 2010 environment

2712595 Microsoft Exchange RPC Client Access service crashes when you run the New-MailboxExportRequest cmdlet in an Exchange Server 2010 environment

2716145 Store.exe crashes on an Exchange Server 2010 mailbox server if a VSAPI based antivirus software is used

2717522 Microsoft Exchange System Attendant service crashes on an Exchange Server 2010 server when you update the OAB that contains a DBCS address list

2720017 An RBAC role assignee can unexpectedly change a DAG that is outside the management role group scope in an Exchange Server 2010 environment

2727802 Microsoft Exchange Replication service crashes intermittently when you try to move mailboxes from an Exchange Server 2003 server to an Exchange Server 2010 server

2733415 Event ID 1 is logged on the Exchange Server 2010 Client Access server in a mixed Exchange Server 2010 and Exchange Server 2003 environment

2733609 Email message and NDR message are not delivered if an email message contains unsupported character sets in an Exchange Server 2010 environment

2743761 DAG loses quorum if a router or switch issue occurs in an Exchange Server 2010 environment

2748766 Retention policy information does not show “expiration suspended” in Outlook Web App when the mailbox is set to retention hold in an Exchange Server 2010 environment

2748767 You receive an NDR message that incorrectly contains recipients of successful message delivery in an Exchange Server 2010 environment.

2748879 You cannot access a mailbox by using an EWS application in an Exchange Server 2010 environment

2749075 A copy of an archived item remains in the Recoverable Items folder of a primary mailbox in an Exchange Server 2010 environment

2749593 Outlook logging file lists all the accepted and internal relay domains in the Exchange Server 2010 organization when you enable troubleshooting logging

2750293 Items remain in the “Recoverable Items\Deletions” folder after the retention age limit is reached in an Exchange Server 2010 environment

2750847 An Exchange Server 2010 user unexpectedly uses a public folder server that is located far away or on a slow network

2763886 “The operation failed” error in the Outlook client when you open a saved message from the Drafts folder and then try to send it in an Exchange Server 2010 environment

Assume that you apply the Update Rollup 4 version 2 for Exchange Server 2010 SP2 (KB2756485), and then you apply the Update Rollup 5 version 1 (KB2719800). In this situation, when you try to run the Get-DatabaseAvailabilityGroup cmdlet, you receive the following error message:

WARNING: An unexpected error has occurred and a Watson dump is being generated: Could not load type ‘Microsoft.Exchange.Rpc.ActiveManager.AmDeferredRecoveryEntry’ from assembly ‘Microsoft.Exchange.Rpc, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’.

Download Update Rollup 5-v2 for Exchange Server 2010 Service Pack 2 (KB2785908)

Exchange 2010 SP1 RU8 and Exchange 2007 SP3 RU9

Today the Exchange CXP team released the following update rollups to the Download Center. All three releases cover Security Bulletin MS12-080. Because this is a security release, the updates will also be available on Microsoft Update.

Update Rollup 8 for Exchange Server 2010 Service Pack 1

Update Rollup 9 for Exchange Server 2007 Service Pack 3

Download: Update Rollup 8 for Exchange Server 2010 Service Pack 1

Download: Update Rollup 9 for Exchange Server 2007 Service Pack 3

Deploy Office 2013 with MDT 2012

When you want to deploy Office 2013 with MDT 2012 you must first create a MSP File and saved in Updates Folder:
How to:  Create custom configurations of Office 2013.

1. Copy de Office 2013 install to the Applications folder

2. Create a application:
image

image

image

image

2. Change the Command Line

image
Change Quiet install Command: setup.exe /adminfile \\servername\deploymentshare$\Applications\Microsoft Office 2013 NL x86\Updates\setup.msp

4. Change the Task Sequence:
image

5. Final Deployment

Rollup 5 for Exchange Server 2010 Service Pack 2

Exchange Team released Rollup 5 for Exchange Server 2010 Service Pack 2.

List with fixes:
2707146 IRM-protected messages cannot be returned in search results if the messages are recorded and sent to an external contact in an Exchange Server 2010 environment

2710975 Some MAPI property objects in an ANSI .pst file contain unreadable characters if you import the file by using the “New-MailboxImportRequest” cmdlet

2712001 ;ExTRA.exe does not collect data if you select a scheduled task for a data collection in an Exchange Server 2010 environment

2712595 Microsoft Exchange RPC Client Access service crashes when you run the New-MailboxExportRequest cmdlet in an Exchange Server 2010 environment

2716145 Store.exe crashes on an Exchange Server 2010 mailbox server if a VSAPI based antivirus software is used

2717522 Microsoft Exchange System Attendant service crashes on an Exchange Server 2010 server when you update the OAB that contains a DBCS address list

2720017 An RBAC role assignee can unexpectedly change a DAG that is outside the management role group scope in an Exchange Server 2010 environment

2727802 Microsoft Exchange Replication service crashes intermittently when you try to move mailboxes from an Exchange Server 2003 server to an Exchange Server 2010 server

2733415 Event ID 1 is logged on the Exchange Server 2010 Client Access server in a mixed Exchange Server 2010 and Exchange Server 2003 environment

2733609 Email message and NDR message are not delivered if an email message contains unsupported character sets in an Exchange Server 2010 environment

2743761 DAG loses quorum if a router or switch issue occurs in an Exchange Server 2010 environment

2748766 Retention policy information does not show “expiration suspended” in Outlook Web App when the mailbox is set to retention hold in an Exchange Server 2010 environment

2748767 You receive an NDR message that incorrectly contains recipients of successful message delivery in an Exchange Server 2010 environment

2748870 Declined meeting request is added back to your calendar after a delegate opens the request by using Outlook 2010

2748879 You cannot access a mailbox by using an EWS application in an Exchange Server 2010 environment

2749075 A copy of an archived item remains in the Recoverable Items folder of a primary mailbox in an Exchange Server 2010 environment

2749593 Outlook logging file lists all the accepted and internal relay domains in the Exchange Server 2010 organization when you enable troubleshooting logging

2750293 Items remain in the “Recoverable Items\Deletions” folder after the retention age limit is reached in an Exchange Server 2010 environment

2750847 An Exchange Server 2010 user unexpectedly uses a public folder server that is located far away or on a slow network

2763886 “The operation failed” error in the Outlook client when you open a saved message from the Drafts folder and then try to send it in an Exchange Server 2010 environment.

Download

Microsoft Office 2013 KMS Volume License Pack

Volume license editions of Office 2013 client products require activation. This download enables IT administrators to set up a Key Management Service (KMS) or configure a domain for Active Directory-Based activation. Either of these volume activation methods can locally activate all Office 2013 clients connected to an organization’s network.

Download

Overview

If you want to activate volume license editions of Office 2013, Visio 2013, or Project 2013 with a KMS host or Active Directory-Based activation, you need to first install Office 2013 Volume License Pack. When an Office 2013 volume edition client is installed, it will automatically attempt to activate via either Active Directory by using its existing domain pairing or a DNS-discoverable KMS host on your organization network. To set up Active Directory-Based activation, you must be running Windows Server 2012, Windows 8, or newer.
All volume editions of Office 2013 client products are pre-installed with a Generic Volume License Key (GVLK) key, which supports automatic activation for both KMS and Active Directory-Based Activation, so you will not need to install a product key.
This download contains an executable file that will extract and install KMS host license files. These license files are required for the KMS host service to recognize Office 2013 KMS host keys. On Windows Server 2012 and volume license editions of Windows 8, you can use your same KMS host key to set up Active Directory-Based activation.

System requirements

Supported operating systems: Windows 7, Windows 8, Windows Server 2008 R2, Windows Server 2012

    • KMS Host: Windows Server 2008 R2, Windows 7 (volume editions), Windows Server 2012, or Windows 8.
    • Active Directory-Based Activation
      • Set-up and Configuration: Windows Server 2012, Windows 8 or newer.
      • Domain controller: Active Directory Domain Services with the Windows Server 2012 schema installed.

Instructions:Microsoft Office 2013 Volume License Pack

  1. You need to perform this step only if you’re setting up a KMS host on Windows Server 2008 R2 or Windows 7 (volume editions). Download and run the update contained in the KB article below. This update enables your Windows Server 2008 R2 or Windows 7-based KMS host to successfully activate Office 2013 clients that are running on Windows 8 or Windows Server 2012:
    KB 2691586
  2. Download and run the executable file on this page on a supported operating system.
  3. Enter your Office 2013 KMS host key when prompted.
  4. Activate the product key online.
  5. If setting up a KMS host, open port 1688 to allow the KMS host service through the firewall:
    1. Open Control Panel and click on the Windows Firewall icon.
    2. Click the “Allow a program through Windows Firewall” link.
    3. Click the Change Settings button.
    4. Check the box for Key Management Service.
  6. To learn more about configuring your KMS host with slmgr.vbs, see the TechNet documentation found on this page.

MAP Toolkit 8.0 Beta released

The MAP Toolkit team announced that MAP Toolkit 8.0 beta is available. MAP Toolkit 8.0 beta has rich feature set to plan and prepare your environment to adopt next wave of Microsoft products and cloud services. The MAP Toolkit has readiness assessments that range from desktop to cloud — Windows 8 to Windows Azure.

The MAP Toolkit 8.0 Beta program is open for general testing today and you need to register to download and try MAP Toolkit 8.0 beta in your environment as you prepare your IT infrastructure to evaluate and deploy the latest Microsoft products and cloud services.

MAP Toolkit 8.0 Beta is available for download here

MAP Toolkit 8.0 has completely revamped modern user interface, which provides easy and clear access to assessment scenarios supported in MAP Toolkit and assessment summaries and results. If you have used a prior version of the MAP Toolkit, you will find MAP Toolkit 8.0 much easier and simpler to navigate, find and run assessment scenarios you are interested and review the assessment results.

image

Following are some of the key assessment scenarios in the MAP Toolkit 8.0:

Windows Server 2012 Readiness

MAP 8.0 Beta assesses the readiness of your IT infrastructure for deploying Windows Server 2012. This assessment includes detailed and actionable recommendations indicating which machines meet Windows Server 2012 system requirements and which may need hardware updates. A comprehensive inventory of servers, operating systems, workloads, devices, and server roles is included to help in your planning efforts.

Windows 8 Readiness Assessment

MAP 8.0 Beta assesses the readiness of your IT environment for a Windows 8 deployment. This assessment evaluates your existing hardware against the recommended system requirements for Windows 8. It provides recommendations detailing which machines meet the requirements and which may need hardware upgrades.

Office 2013 and Office 365 Readiness Assessments

MAP 8.0 Beta assesses readiness for Office 2013 and provides an in-depth assessment of client desktops for upgrading or migration. It also offers support for Office 365 features such as web apps, Exchange Online, SharePoint Online, or full Office 365 client support.

Windows Azure Virtual Machines Migration Recommendation

MAP 8.0 Beta performs a comprehensive assessment of Windows Server and Linux machines to determine if a migration to Windows Azure Virtual Machines is possible. The toolkit then offers suggested changes to prepare the machines for migration. Key features help you reduce the operating costs of hosting on-premise servers as well as estimating the required size and monthly network and storage usage required to migrate on-premise Windows and Linux servers to Windows Azure Virtual Machines using the data from the environment.

Software usage assessment for Lync

MAP 8.0 Beta’s Lync Enterprise and Usage Tracking feature counts the number of Lync Enterprise/Plus users as well as device activities for determining the number of required client access licenses (CAL). For Lync 2010, MAP provides a server inventory and software usage by device and user for Lync Standard features. MAP’s updated Software Usage Tracking feature provides consistent software usage reports for key Microsoft products including Windows Server, SQL Server, System Center, Forefront Endpoint Protection (FEP), and Lync.

Starting today, beta program will be open for six weeks and will end on Dec 14th, 2012. You can participate in beta by downloading and running MAP Toolkit 8.0 beta in your environment.

MAP Toolkit 8.0 Beta is available for download here

Translate »