According to a recent Post from mine (Part 1), here are my issues with the System Center Configuration Manager addition. As you can see on the following print screen, ConfigMgr detects the Language of the keyboard:
Today I would like to share my experience when it comes to add a User Agent (e.g. Browser) to the list of Single Sign On capable applications. There is quite a good Article from Microsoft that describes how to add a User agent to the ADFS Configuration, you will find this Article here:
Today I would like to show you, how you can easily create and deploy an Office 365 Application within Microsoft System Center Configuration Manager Console.
Within the ConfigMgr Console navigate to the “Office 365 Client Management” Dashboard, and click on “Office 365 Installer”:
Today I wanted to sequence a new package with the Microsoft Application Virtualization (App-V) Sequencer Tool, but I had no success. I always got the following error when the installation should start:
“Cannot start service AppVMon on computer ‘.’.”
Let me say: This is an unsupported scenario
Today I decided to do an in place upgrade of my LAB Installation, which means to switch from Microsoft Server 2012 R2 to Server 2016 as operating System. Before I started that upgrade, I made sure to have a proper backup of the database and the cd.latest Folder, because this is a single box installation.
Then I mounted the Server 2016 ISO and started with the installation. The installation itself took quite a while, but it ran through without an error. When I saw that the virtual machine was ready to logon, I actually tried to use RDP, without success. I then logged on through the Hyper-V Console and checked the System Center Configuration Manager Console, and for my surprise, the console started up and had also no error.
I checked the Component status and recognized a lot of issues, which led me to check the IIS Service (World Wide Web Publishing Service; W3SVC). This Service was not started, the startup type was on “Disabled”. Continue reading
Today I would like to show you, how you can implement an Upgrade of a Windows 10 Installation through the Servicing Option.
I always think of two things, when I have to decide to use an Upgrade Task Sequence or the Servicing Model, and those are:
But for this blog post, I would like to show my setup for the servicing model.
First of all, I have already written a post about the Update process in a slightly overview manner, you will find this post here: My old post
The first step would be to determine which packages you would like to implement for the upgrade. Based on the fact, that I use English as base language, I will add the Feature on Demand (FoD) packages, and I will also add the feature package NetFx3. My Setup does also contain the German Langauge, which requires me to add the corresponding Language Pack and FoD Packages. The following picture shows the folder of my Packages which I want to include within the Windows 10 Installation:
today I would like to share my knowledge about the MCSE Certification Path, if you got one already. This means, in my case, I’ve got the MCSE: Mobility (without a year at the end):
But I can also achieve the MCSE: Mobility 2017:
this is a small one: I had an issue when I tried to use the RMS Sharing app. Always when I used the Sharing application, I got the following error:
0x800704cf the network location cannot be reached
Unfortunately I haven’t saved a Screenshot of the error Message. But I could not find any information on this topic. The only thing I was thinking about was: Why does the error tell me, that the sharing app can’t connect to a network location. Continue reading
Today I would like to talk about the upcoming update cycles you have to do, when you are using Windows 10 Current Branch or Current Branch for Business. This means, if you have started to install Windows 10 1507 (which represents the first Windows 10 Release, some may call it also RTM) in spring of last year, you will be soon required to upgrade to a newer version of Windows 10. Also if you are using Windows 10 1511, with the upcoming creators update, the 1511 version of Windows 10 will be soon unsupported, following the official guidelines.
Currently many customers are looking for a solution to protect their content, and finding themself within the Microsoft Office 365 and Azure Ecosystem, and realizing, that they might already been able to use a solution for Information Protection. But this leads often to the Question, how can I, and more important, how can my users take advantage of Azure Information Protection (AIP)?
I will try to answer those questions within this Blog Post.