Search This Blog

Friday, July 29, 2016

Cannot add Azure App Service to a network (VNET) with static routing

When you work with Azure, occasionally you step on some technical limitations.
This time developers had designed a solution were a WebJob (Azure App Service) would be created in Azure, but it would connect to on-premises network to the database.

In this case Site-to-Site nework for VNET was created with static routing because of limitation in on-premises firewall.

When we tried to add the WebJob (Azure App Service) to this VNET we received an error that it can be added only to networks with dynamic routing.

As explained here https://azure.microsoft.com/en-us/documentation/articles/web-sites-integrate-with-vnet/ that is the limitation of Azure App Services, because it connects to network with small VPN module and that technology depends on dynamic routing.

The easiest solutions here are to use Azure App Service Environemt (which is a Premium feature and thus costs more) or Hybrid Connections (https://azure.microsoft.com/en-us/documentation/articles/integration-hybrid-connection-overview/)

Thursday, July 28, 2016

What happens when you click Update in SCEP

I have always wondered what exactly happens when you open SCEP client interface and click Update button.. from where does the SCEP client tries to install updates?

Here here is the short explanation of what happens, when you click Update in SCEP client:
1) SCEP does not search for updates directly in SCCM;
2) SCEP uses defined definion updates search order defined by antimalware policy created in SCCM.
3) If you have defined only SCCM as definition update source in antimalware policy, then update installation fails.

So if you have configured sources like this:
then SCEP Update button would first try to connect to WSUS, then Microsoft Update.


Wednesday, July 27, 2016

Force SCCM 1606 update to appear in console

If the SCCM 1606 update does not appear in console, then use this script https://gallery.technet.microsoft.com/ConfigMgr-1606-Enable-043a8c50 and follow setup instructions to force the update to appear in console.

Upgrade to SCCM 1606 free disk space requirements

If you want to upgrade to SCCM 1606, but prerequisite check fails saying that there is not enough free disk space, then you should free up at least 15 GB and then the error will be gone.

Tuesday, July 26, 2016

Find calendar event created date and time in Outlook

Because of conflicting appointments in calendar I was asked to find when calendar event was created in Outlook.
It was not as easy as it seemed it should be, but here is a solution:
1) Open Outlook
2) Open Calendar
3) Select View -> Change View -> List
4) Right-click on column header and select Field Chooser:

5) Find filed "Created" and drag-and-drop it onto column header
6) You will see created time of every calendar item!

Monday, July 25, 2016

SOLVED: An authentication error has occured (Code: 0x80090304).

Today I was trying to connect with Remote Desktop from a Windows Server 2008 host to a Windows Server 2012 R2 host, but connection after entering password didn't succeed.

The error was "An authentication error has occured (Code: 0x80090304)." I had never seen such error before. The error translates as "The Local Security Authority cannot be contacted".

After some troubleshooting I decided to reset the password, which did the trick. I was able to connect afterwards :)

SCCM Update scan failed (Failed to run BeginSearch on WUAgent. Error = 0x80080005.)

After a small vacation I am back :)
So today I saw a dozen of computers which failed updates evaluation in a SCCM 2012 R2 infrastructure. Inspecting SCCM client logs revealed a "Failed to run BeginSearch on WUAgent. Error = 0x80080005." in WUAHandler.log. This seems to be a generic Windows Update error which means that Windows Update (wuauserv) is not started. After starting the service update scans succeeded and updates installed without any problem.

Of course you should try to find a reason why Windows Update service was stopped, because this is not a normal Windows configuration.

Sunday, July 3, 2016

How does SCCM chooses boot image architecture for PXE

If you have ever used operting system deployment with SCCM and not just SCCM, then you know that before installing full OS computer boot in Windows Preinstallation Environment (WinPE). This WinPE is usually called a boot image.

Let's get to the subject - when using SCCM with PXE, x64 or x86 boot image can be loaded. But what happens when computer is advertised with both x64 and x86 Task Sequences how do you control which boot image to load?

The answer is simple - with SCCM it is not possible to control which boot image is loaded. The SCCM loads the boot image for last deployed Task Sequence.

The consequence of this is, for example, that if you booted a x86 boot image then after choosing to deploy a x64 Task sequence the first thing would be to download a x64 boot image and reboot and only then execute the Task Sequence.

A possible solution for this could be to create a separate collections for x64 and x86 computers and only deploy appropriate Task Sequences. For new computers you would first have to import computer to the necessary collection.