Use any Windows key with your Windows 7 ISO
article #768, updated 10 days ago

From the amazing Matt Quick. The “eicfg removal utility” here:

http://code.kliu.org/misc/winisoutils/

will take a Windows 7 ISO of any version, and convert it into one which will install whichever version is appropriate for your OS key. Detailed instructions are here:

https://mattthequick.wordpress.com/2015/01/13/create-all-in-one-windows-7-install-media-by-removing-ei-cfg/

Categories:   Windows OS-Level Issues   

==============

Automatically backup PSTs
article #772, updated 10 days ago

From the amazing Matt Quick:

https://mattthequick.wordpress.com/2015/01/15/how-to-automatically-back-up-your-pst-in-outlook/

Automatic PST backups for Outlook versions 2002, 2003, 2007:

http://www.microsoft.com/en-us/download/details.aspx?id=9003

Can be made to work with Outlook 2010:

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

And something new for Outlook 2013:

http://outlookbackupaddin.codeplex.com/

Categories:   Outlook   

==============

Connect to Office 365 via PowerShell
article #804, updated 10 days ago

Contributed by the excellent Matt Quick:

https://mattthequick.wordpress.com/2015/11/25/connect-to-office-365-via-powershell/

Categories:   Exchange and Exchange Online   Office 365

==============

Outlook Autodiscover After Migrating To Office 365 / Exchange Online
article #839, updated 10 days ago

After migrating all email accounts from an on-premises Exchange 2008 or later server to Exchange Online, there remains the problem of what to do about new Outlook profile creation. Outlook will still look for the old server name, and especially if you want to keep the old server alive for a while, you will have significant problems getting Outlook 2013 to do anything with Exchange Online. Here is what the extraordinary Matt Quick and I did recently with beautiful results.

For the sake of this discussion, “localdomain.local” is the LAN-local AD-enabled domain, and “publicdomain.pub” is the Internet domain. The on-prem Exchange originally had local DNS name “exchange.localdomain.local” and Internet DNS name “exchange.publicdomain.pub”.

  1. Migrated all mailboxes from on-premises Exchange 2010 to Exchange Online. Dirsync was used for initial account setup, then turned off for the actual copyover process which was done with MessageOps.
  2. In Exchange Management Shell, ran Get-ClientAccessServer to get the canonical name of on-prem Exchange (we’ll say it was EXCHANGENAME), and then Set-ClientAccessServer -Identity EXCHANGENAME -AutoDiscoverServiceInternalUri $NULL (replacing EXCHANGENAME with the actual name) to nullify as many defaults as possible.
  3. Set autodiscover.localdomain.local as a CNAME to autodiscover.outlook.com.
  4. Set autodiscover.publicdomain.pub as a CNAME to autodiscover.outlook.com in Internet DNS. This LAN has a local copy of publicdomain.pub in its domain controllers, so copied this record to the local server as well.
  5. Unregistered the NIC for the on-premises Exchange server in DNS. The checkboxes are in the DNS tabs of both TCP/IPv4 and TCP/IPv6, within the Advanced area of the NIC. This is done so that DNS changes which are next, will not be undone automatically.
  6. Removed DNS A records exchange.localdomain.local and exchange.publicdomain.pub from local and Internet DNS respectively.
  7. Added DNS CNAME records exchange.localdomain.local and exchange.publicdomain.pub, both pointing to outlook.office365.com, to local and Internet DNS as appropriate.
  8. Set up oldexchange.localdomain.local and oldexchange.publicdomain.pub as A records pointing to the IP being used by the on-premises Exchange, to local and Internet DNS as appropriate, for archival uses and until we are ready to decommission the on-prem Exchange altogether.

Categories:   Exchange and Exchange Online   Office 365

==============

Installing the GUI onto Windows Server 2012 Core
article #853, updated 10 days ago

The indefatigable Matt Quick provides thus:

http://prajwaldesai.com/switching-between-gui-and-server-core-in-windows-server-2012/

Categories:   Servers   Windows OS-Level Issues

==============

Bluescreen at boot with win32k.sys error
article #1022, updated 10 days ago

If Windows 7 won’t boot all the way, if it gives a bluescreen involving win32k.sys, it may be a bad update. Boot into startup repair and rename FNTCACHE.DAT in system32 to .OLD. That forces Windows to make a new one and boot will occur next time.

Courtesy of the excellent Matt Quick.

Categories:   Windows OS-Level Issues   

==============

A tool to retrieve, examine, and test SSL certs in servers
article #1085, updated 10 days ago

From the excellent Matt Quick:

http://www.netscantools.com/ssl-certificate-scanner-standalone.html

Categories:   Certificates   Web Methods

==============

Optimize Service Work Items and Additional/Delayed Worker Threads
article #1084, updated 11 days ago

Downloadable here within OWTAS.ZIP, is a VBS script which sets a number of additional critical and delayed worker threads, plus service work items. The number is autocalculated according to a combination of RAM and OS bit-width (32 vs. 64).

Categories:   Windows OS-Level Issues   

==============

"Failed to schedule Software Protection service for re-start" Error Code: 0x80070005
article #1083, updated 11 days ago

One way this can be fixed at least sometimes, is to give “NETWORK SERVICE” full rights to:

C:\Windows\System32\Tasks\Microsoft\Windows\SoftwareProtectionPlatform

Categories:   Windows OS-Level Issues   

==============

How to Install Microsoft ADMX Group Policy Templates
article #1082, updated 12 days ago

  1. The package is usually downloaded as a self-extracting EXE. Extract it to a useful location.
  2. Copy all of the .ADMX files from the admx folder, into \\domain.local\SYSVOL\domain.local\Policies from a domain controller, where domain.local is the full Active Directory domain.
  3. Copy all of the .ADMX files from the admx folder, into C:\Windows\PolicyDefinitions on every domain controller.
  4. Copy all of the .ADML files from admx\en-us, into \\domain.local\SYSVOL\domain.local\Policies\en-us on a domain controller, where domain.local is the full Active Directory domain.
  5. Copy all of the .ADML files from admx\en-us, into C:\Windows\PolicyDefinitions\en-US on every domain controller.
  6. If other languages are used on premises, ditto other language folders (en-us being one).

Categories:   Group Policy