Category: Microsoft

578:0x000004DC:0x0000001D Send-As permission with Outlook 2010 Exchange 2007

578:0x000004DC:0x0000001D Send-As permission with Outlook 2010 Exchange 2007
Error:

myaddress@mydomain.com
You are not allowed to send this message because you are trying to send on behalf of another sender without permission to do so. Please verify that you are sending on behalf of the correct sender, or ask your system administrator to help you get the required permission.

Diagnostic information for administrators:

Generating server:

myaddress@mydomain.com

#MSEXCH:MSExchangeIS:/DC=com/DC=mydomain:SERVERNAME[578:0x000004DC:0x0000001D] #SMTP

Solution:
1.Close Outlook

2.Delete the offline address book folders in

Windows 7: C:\Users\username\AppData\Local\Microsoft\Outlook\Offline Address Books
Windows XP: C:\Documents and Settings\username\Local Settings\Application Data\Microsoft\Outlook\Offline Address Books

3.Open Outlook and let it download a new copy of the offline address book.

3.1 Send/Receive Tab
3.2. Send/Reveive Groups
3.3 Download Address Book
3.4 Choose Full Details and \Global Address List

Group Policy Settings Reference for Windows 8 and Windows Server 2012

These spreadsheets list the policy settings for computer and user configurations that are included in the Administrative template files delivered with the Windows operating systems specified. You can configure these policy settings when you edit Group Policy Objects.

You can use the filtering capabilities that are included in this spreadsheet to view a specific subset of data, based on one value or a combination of values that are available in one or more of the columns. In addition, you can click Custom in the drop-down list of any of the column headings to add additional filtering criteria within that column.
To view a specific subset of data, click the drop-down arrow in the column heading of cells that contain the value or combination of values on which you want to filter, and then click the desired value in the drop-down list. For example, to view policy settings that are available for Windows Server 2012 or Windows 8, in the Administrative Template worksheet, click the drop-down arrow next to Supported On, and then click At least Microsoft Windows Server 2012 or Windows 8.

What’s New?

The Administrative Template spreadsheet contains three columns that provide more information about each policy setting’s behavior related to reboots, logoffs, and schema extensions. These columns are the following:

  • Reboot Required: A “Yes” in this column means that the Windows operating systems requires a restart before it applies the described policy setting.
  • Logoff Required: A “Yes” in this column means that the Windows operating system requires the user to log off and log on again before it applies the described policy setting.
  • Active Directory Schema or Domain Requirements: A “Yes” in this column means that you must extend the Active Directory schema before you can deploy this policy setting.
  • Status: A “New” in this column means that the setting did not exist prior to Windows Server 2012 and Windows 8. It does not mean that the setting applies only to Windows Server 2012 and Windows 8. Refer to the column entitled “supported on” to determine to which operating system the policy setting applies.

WindowsServer2012andWindows8GroupPolicySettings.xlsx
Group Policy Settings Reference for Windows 8 and Windows Server 2012

BINK

Windows Assessment and Deployment Kit (ADK) and vSphere 4 does not work together

When you using vSphere 4 and and using MDT 2012 update1 with Windows Assessment and Deployment Kit you run in de following error. Same thing wil also with Workstation 8.clip_image001

Solution 1: Do not install Windows Assessment and Deployment Kit on your MDT Server. You can still using MDT 2012 Update 1 with waik 3.5 if not deploying Windows 8 or Windows 2012 right now.

Solution 2: Upgrading you vSphere server to the latest version (5.1) or Upgrade Workstation to latest version (Version 9).

Troubleshooting Windows Deployments

Michael Niehaus created a troubleshooting guide about MDT

Check out: Troubleshooting Windows Deployments 2012-09-11.pdf

Copying $OEM$ files and folders with MDT 2012 Update 1

MDT 2012 Update 1 no longer uses SETUP.EXE to install Windows 7 and above. One side effect of this is that $OEM$ folders are no longer going to be copied, since that was something that SETUP.EXE did that the MDT LTIApply.wsf script doesn’t handle.

I’ve never been a big fan of using the $OEM$ folder structure, as it’s just as easy to add explicit XCOPY steps into the task sequence. But for those of you out there that are using them, you can leverage the attached script (CopyOEM.zip) in your task sequence to do that.

To set this up, first copy the script into your deployment share. Then, add a new step to the task sequence right after the “Install Operating System” step to run the script. It should look like this:

CopyOem

Now, it will follow the original MDT logic for locating the appropriate $OEM$ folder to use, checking in this order:

  • %DeployRoot%\Control\%TaskSequenceID%\$OEM$
  • %SourcePath%\$OEM$
  • %DeployRoot%\%Architecture%\$OEM$
  • %DeployRoot%\$OEM$

where %DeployRoot% is the path to the deployment share, %TaskSequenceID% is the ID of the running task sequence (e.g. WIN8), %SourcePath% is the path within the deployment share for the operating system being used, and %Architecture% is either X86 or X64, depending on the boot image being used.

Once it finds a folder, it will look for two folders in that $OEM$ folder and copy them to the appropriate place for the new OS:

  • $1 will be copied to the root of the volume that the new OS image was applied to.
  • $$ will be copied to the Windows folder on the volume that the new OS image was applied to.

The script doesn’t deal with any other folders because it’s too messy to do that from within Windows PE – drive letters aren’t the same as what they would end up being in the full OS

Download: CopyOEM.zip

Source: Copying $OEM$ files and folders with MDT 2012 Update 1

MDT Displaying the task sequence name

When you configure MDT you could specify an organization name  To specify these, you can configure them in CustomSettings.ini:

_SMSTSOrgName=WardVissers
_SMSTSPackageName=My Package Name

That’s great if you want to hard-code the values, but what I wanted was that _SMSTSPackageName  is set to the name of the task sequence that is being executed. That’s a little harder to do, because the task sequence hasn’t yet been selected when CustomSettings.ini is being processed, and you can’t set these read-only variables once the task sequence has started.

So this is one of those cases where you have to modify one of the MDT scripts, in this case LiteTouch.wsf. Fortunately, it’s a really trivial change. Look for this line:

oEnvironment.Item("_SMSTSPackageName") = "Lite Touch Installation"

And change it like so:

oEnvironment.Item("_SMSTSPackageName") = oEnvironment.Item("TaskSequenceName")

That line is only executed if _SMSTSPackageName is blank after CustomSettings.ini has been processed, so it won’t have any effect if you manually configured a value in CustomSettings.ini.

With that change, you can now see the name of the currently-running task sequence:
IMG_20120903_155124

You can download the file here: LiteTouch.7z (Tested with MDT 2012 Update 1)

Microsoft Virtual Machine Converter Solution Accelerator

The Microsoft Virtual Machine Converter (MVMC) Solution Accelerator is a Microsoft-supported, stand-alone solution for the IT pro or solution provider who wants to convert VMware-based virtual machines and disks to Hyper-V®-based virtual machines and disks.

MVMC provides the following features:

  • Converts and deploys virtual machines from VMware hosts to Hyper-V hosts including Hyper-V on Windows Server® 2012. As part of the machine conversion MVMC converts the virtual disks attached to the source virtual machine. It also migrates configuration such as memory, virtual processor and so on from the source virtual machine to the converted virtual machine deployed on Hyper-V. It adds virtual network interface cards (NICs) to the converted virtual machine on Hyper-V.
  • Converts VMware virtual disks to Hyper-V based virtual hard disks (VHDs).
  • Supports conversion of virtual machines from VMware vSphere 4.1 and 5.0 hosts to Hyper-V.
    • Note MVMC also supports conversion of virtual machines from VMware vSphere 4.0 if the host is managed by vCenter 4.1 or vCenter 5.0. You have to connect to vCenter 4.1 or 5.0 through MVMC to convert virtual machines on vSphere 4.0.
  • Offers fully scriptable command-line interfaces for performing virtual machine and disk conversions that integrates well with data center automation workflows and Windows PowerShell scripts.
  • Has a wizard-driven GUI, making it simple to perform virtual machine conversion.
  • Uninstalls VMware tools prior to conversion to provide a clean way to migrate VMware-based virtual machines to Hyper-V.
  • Supports Windows Server guest operating system conversion, including Windows Server 2008 R2, Windows Server 2008 and Windows Server 2003 SP2.
  • Enables conversion of Windows® client versions including Windows 7.
  • Installs integration services on the converted virtual machine if the guest operating system is Windows Server 2003 SP2.

System requirements

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

Before you install MVMC, you must install the following software on the computer on which MVMC will run:

  • Operating systems: Windows 7, Windows Server 2008 R2, or Windows Server 2012 (full installation)
  • Microsoft .NET Framework 3.5 and Microsoft .NET Framework 4 if installing MVMC on Windows 7 or Windows Server 2008 R2
  • Microsoft .NET Framework 4.5 if installing MVMC on Windows Server 2012

Download

Updated eBook Introducing Windows Server 2012 RTM Edition

Mitch Tulloch and the Windows Server team have released a new updated version of the FREE e-Book for IT professionals: Introducing Windows Server 2012 RTM Edition. This book is a great way to get quickly skilled up on all the new improvements in this latest Windows Server – one of the most ambitious releases of Windows Server for IT Pros since Active Directory was released in Windows Server 2000! In this 256-page eBook, you’ll find 5 chapters of detailed technical content covering the following key improvements to building a Private Cloud at your shop with Windows Server 2012:

2012bookrtm

Get it for free by posting a tweet Smile

Updated eBook for IT Pros on Windows Server 2012

List of Performance hotfixes for Windows 7 SP1

Applies to:
Windows 2008 R2 SP1
Windows 7 Service Pack 1
Windows 7 SP1

Article ID: 2505438 – Slow performances in applications that use the DirectWrite API on a computer that is running Windows 7 or Windows Server 2008 R2
http://support.microsoft.com/?id=2505438

Article ID: 2505454 – The startup process is delayed on a computer that has a large hard disk installed and is running Windows 7 or Windows Server 2008 R2
http://support.microsoft.com/?id=2505454

Article ID: 2510636 – An update that improves the startup performance of Windows 7 and of Windows Server 2008 R2 is available
http://support.microsoft.com/?id=2510636

Article ID: 2523887 – You may encounter file corruption issues when you use the Offline Files feature to synchronize data in Windows 7
http://support.microsoft.com/?id=2523887

Article ID: 2524478 – The network location profile changes from "Domain" to "Public" in Windows 7 or in Windows Server 2008 R2. This problem can affect Group Policy processing at boot time because NLA does not know what network profile to use.
http://support.microsoft.com/kb/2524478

Article ID: 2525332 – You encounter a long logon time after you enable the "Do not automatically make redirected folders available offline" Group Policy setting in Windows 7 or in Windows Server 2008 R2
http://support.microsoft.com/?id=2525332

Article ID: 2555428 – The Windows 7 startup process is slow when you create many restore points
http://support.microsoft.com/?id=2555428

Article ID: 2561285 – You experience a long domain logon time in Windows 7 or in Windows Server 2008 R2 after you deploy Group Policy preferences to the computer
http://support.microsoft.com/?id=2561285

Article ID: 2561708 – Offline files synchronization may not finish on a computer that is running Windows 7 or Windows Server 2008 R2
http://support.microsoft.com/?id=2561708

Article ID: 2581608 – Logon scripts take a long time to run in Windows Vista, in Windows Server 2008, in Windows 7 or in Windows Server 2008 R2
http://support.microsoft.com/kb/2581608

Article ID: 2582112 – Windows 7 or Windows Server 2008 R2 stops responding when an application performs many I/O operations to a network share
http://support.microsoft.com/?id=2582112

Article ID: 2610379 – The Folder Redirection policy does not work if a previous user sets a redirected folder to an offline mode in Windows 7 or in Windows Server 2008 R2
http://support.microsoft.com/?id=2610379

Article ID: 2617858 – Unexpectedly slow startup or logon process in Windows Server 2008 R2 or in Windows 7
http://support.microsoft.com/?id=2617858

Article ID: 2625434 – "ERROR_SHARING_VIOLATION" error message in Windows XP or in Windows Server 2003 when you try to open a file on an SMB share on a server that is running Windows 7 or Windows Server 2008 R2
http://support.microsoft.com/?id=2625434

Article ID: 2640148 – Windows Explorer stops responding if you try to expand a mapped drive in Windows 7 or in Windows Server 2008 R2
http://support.microsoft.com/kb/2640148

Article ID: 2645611 – Windows 7 or Windows Server 2008 R2 stops responding if you try to log on a computer that has multiple monitors
http://support.microsoft.com/?id=2645611

Delay occurs when you log on to a domain from a computer that is running Windows 7 or Windows Server 2008 R2
http://support.microsoft.com/?id=2709630

Article ID: 2709630  2690528 Slow performance when you browse the My Documents folder in the document library in Windows 7 or in Windows Server 2008 R2

http://support.microsoft.com/kb/2690528/en-us

An update is available for Windows 7 and Windows Server 2008 R2 KMS hosts to support Windows 8 and Windows Server 2012

This update extends the Key Management Service (KMS) for Windows 7 and Windows Server 2008 R2 to allow enterprise licensing of Windows 8 and of Windows Server 2012.
KMS provides support for the following KMS client activations:

  • Windows Server 2008 R2 and Windows Server 2008 R2 Service Pack 1 (SP1)
  • Windows Server 2008 and Windows Server 2008 Service Pack 2 (SP2)
  • Windows 8
  • Windows Server 2012
  • Windows 7 and Windows 7 Service Pack 1 (SP1)
  • Windows Vista and Windows Vista Service Pack 2 (SP2)

Key Management Service (KMS) uses a KMS host key to activate KMS on a KMS host, and to establish a local activation service in your environment. This update extends support for KMS to provide activation for Windows 8 and for Windows Server 2012.

Download

Translate »