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