Windows 10 randomly goes blank and lock screen displays on wakeup

So this is a strange one.  You set all the power settings correctly and yet every now and again the system goes into suspend mode.  This can be terribly annoying because you have to put in your credentials to unlock the screen after coming out of suspend.  And worse yet, this can happen in as short of a time as two minutes!  Yes, 2 minutes.

Turns out the standard time out when a computer is left unattended with no user logged in is two minutes.  But, here’s the rub, you can’t change that by default!  Now you may ask why in the world would that setting even come in to play if the user is still logged in?  That’s a good question and likely a bug (or feature if you are a Softy).  In any case one fix for this annoying situation is to uncover the unattended timeout setting via a registry setting change.

Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\238C9FA8-0AAD-41ED-83F4-97BE242C8F20\7bc4a2f9-d8fc-4469-b07b-33eb785aaca0
Double click on Attributes
Enter number 2.

Now go back to advanced power settings in the power control panel/power plan.  You should see the “system unattended sleep timeout” setting which will be set to 2.  change it to something longer or zero which will disable unattended sleep.

This bug/feature is present in windows 10 up through 1803 at least.

More on this.  Why does this appear to be random?  Well, it’s not really random.  There is another hidden setting that has an affect on this.  Its called “Allow sleep with remote opens”  and by default it is set to On under battery power and OFF when under AC power.  So what is a remote open?  Terminal emulation?  Nope.   Outlook Email?  Nope.  Web browsing?  Nope.  A document that is saved on a server?  YES.   So the user may not realize what they have open when the mysterious sleepy time hits.  And good luck in getting an accurate answer when you ask them about what they do or don’t have open.

No Comments

Windows 10 and when shutdown isn’t really shutting down.

Windows 10 is soooo stable it doesn’t ever really need to be shutdown.  Or that appears to be the belief at Redmond these days.  Well we all know that is a big pile of manure.  In their infinite wisdom MS has set the default action of shutdown in windows 10 to turn the machine off, but not really.  The machine goes off but it saves the state  of memory so that when you turn it back on, it just picks up where it left off.  Pretty much like the old Hibernate behavior from the Windows 7 and earlier days.  But here’s the thing, they don’t tell you that’s what is happening or any obvious way of changing the behavior.  In fact the only way you find out that windows never really shuts down is that when you look in the system log, you never see an event log event stating that it was started, which means it never shut down.  Turns out this is a behavior caused by a power setting in Windows 10.  Find the Settings page for Default power buttons. (It’s under the “Chose what the power button does” heading on the left side in the power options section of control panel - at least until they move it again)  On that page the first shutdown setting item is “Turn on fast startup (recommended)” .  By default that is checked.  Uncheck that setting and from now on, when you tell your system to shutdown, not only will it power off, but when you start up, windows will actually start from scratch instead of the state it was in when you shutdown.  Off is now really off.

No Comments

Missing OAB in migration to Exchange 2013

If you have deployed Exchange 2013 within an environment with Exchange 2007 or 2010 already deployed, you may experienced issue when downloading OAB with Outlook for users which have been moved to Exchange 2013 (Outlook Send/Receive generates 0×8004010F An object cannot be found error or Microsoft Exchange offline address book 0X8004010F error in the synchronization issues folder).

If you check autodiscover settings via Outlook “Test E-mail Autoconfiguration” (Ctrl-Rightclick outlook icon in systray) you may see no OAB URL defined – there is no URL neither no OAB parameter.

To solve this issue, Run the following command from EMS on the Exchange 2013 server: Get-offlineaddressbook | fl WebDistributionEnabled,VirtualDirectories,Identity

If you have WebDistributionEnabled set to False and/or no value defined for VirtualDirectories, this is why you have the issue

To solve this issue, run the following command

Get-ClientAccessServer | Get-OabVirtualDirectory | fl identity to get OAB virtual directory identity (this will be required for the next command)

Set-OfflineAddressBook -VirtualDirectories “” –Identity

Wait a little bit, recycle the MSExchangeAutodiscoverAppPool and try a new autodiscover check; you should now have OAB URL parameter and value.

No Comments

Moving copiers to 2008 server

Older copiers that you got scanning working to 2003 servers may not work on 2008 and above servers. It seems that MS “enhanced” the SMBv2 protocol in 2008 and now reject SMBv2 requests if the requester doesn’t support extended attributes (whatever those are) In any case, the fix is to set the server to allow legacy SMBv2 negotiation as follows:

1.Open Registry Editor. To do this, click Start, type regedit in the Start Search box, and then press ENTER.
2.Locate and then right-click the following registry subkey:

3.On the Edit menu, point to New, and then click DWORD (32-bit) Value.
4.Type AllowLegacySrvCall, and then press ENTER.
5.Right-click AllowLegacySrvCall, and then click Modify.
6.Type 1 in the Value data box, and then click OK.
7.Exit Registry Editor.
No reboot necessary.


No Comments

Edit the registry contained in a Wim File

How to open a wim and edit the registry….

•Open the Deployment Tools Command Prompt (Contained in the Microsoft Windows AIK folder on your start menu)
•Mount your wim file, by entering the below command . Substitute the filename, index and mount directory for your wim filename and image index. The mount directory just needs to be an empty pre-existing directory.

dism /mount-wim /wimfile:C:\WimImages\Win7.wim /index:2 /mountdir:C:\AIKMount
•Once DISM reports that the image has been mounted successfully, you need to mount the registry. I’m going to mount the wim’s HKLM\Software hive in this example. You’ll notice the root of my reg path below is the folder I mounted the WIM into, given in the previous command. Type

•Open RegEdit and load the software registry hiver from the mounted image (it’s in the c:\windows\system32\config folder) Make your changes.
•Once you are finished, Unload the hive and exit Regedit.
•Unmount the wim image and commit the changes back into the .wim file.
dism /unmount-wim /mountdir:C:\AIKMount /commit

If you want to not save the changes use the /discard switch instead of /commit


No Comments

WDS Multicast is really slow!

When using WDS to load images, direct SMB unicast works fine but overloads the network and/or server if you have too many sessions. So we try Multicast and that goes incredibly slow! What is going on? There is all sort of info on how to “tune” multicast, but the most likely culprit is your network switches, especially if you have HP procurve switches. There are two things to do. 1) make sure IGMP snooping is turned on for the VLAN you are using. Do this by getting into config mode and issuing the following vlan 1 ip igmp (if you want to enable it on VLAN 1). 2) Change the default mulitcast IP range in WDS from - to - because apparently the default range is ignored by IGMP on ProCurve switches. Nice!

Speeds should be back up to blazing after this.


No Comments

Access denied attempting to access windows 7 administrative shares in a workgroup.

Getting Rid of the “Access Denied” Error Message

To solve this issue you need to make a small registry modification on the TARGET computer.

Use Regedit to add a dword value named LocalAccountTokenFilterPolicy to the following key and set it to “1″

Note: To revert to the original setting, change the LocalAccountTokenFilterPolicy value to 0 (zero).

Next, try to access the administrative share on the remote machine. This time you should succeed

No Comments

@#$@#%#$% Gmail has blocked me!

you’ve had an “event” on your email server and now you’re on all kinds of RBLs. You get yourself off all the bad guy lists, but google is still blocking you with a message that looks something like this:
550-5.7.1 [x.x.x.x] Our system has detected that this message is likely unsolicited mail. To reduce the amount of spam sent to

or #5.5.0 smtp;550-5.7.1 [x.x.x.x] Our system has detected an unusual rate of ……

And you find that google doesn’t have a way to get yourselves off their list. Can you say 1-800-wedontgiveadamn? There is an I can’t send mail to you guys form that you can fill out here: but don’t hold your breath.

The one thing you CAN do, however, is make sure you have an SPF record setup on your sending domain. If you don’t have one setup, setting one up will almost instantly release the block by Google.

To setup an SPF record, simple add the following txt record under a host id of @.
v=spf1 mx ptr ip4:x.x.x.x ~all

And then tell everyone that google is the new evil empire (along with apple and microsoft).


Citrix App won’t launch

Citrix app won’t launch in windows 7/Vista and IE9.  you get the “Do you want to open or save this file” dialog when you try to launch it.  IE reset doesn’t fix it, niether does changing the security zone.  Try executing the following:  c:\Program Files (x86)\Citrix\ICA Client\wfica32 /setup  Nope - I don’t know what all that does - other than make it work :)

No Comments

WOL not working from new server

When moving things from an old server (that happenes to be running Windows 2008 R2 (64bit)) WOL does not seem to get to anything. It worked on the old server but not on the new one. WTF? First thoughts are something 2008 R2 related or 64bit related. It turns out it probably isn’t any of that. It’s probably the fact that newer servers tend to have multiple NICs and your older hardware only had a simgle NIC. What is going on is that even though the extra NICs aren’t used, as long as they are active (not diabled) then WOL will use one to send it’s packets. Don’t know yet how to reorder the NICs so WOL usues the active one so the simple fix is to diable the NICs that aren’t plugged in to the network. WOL then has to use the active one and it works fine. Jeesh.


No Comments