Monthly Archives: November 2015

SCCM-Software Update Compliance taking long time

Hi All, have you ever wonder why the Software Update Compliance takes long time to report the correct date? often that I get this question from a customer that wants to know what the status just after a software update deployment, but when I mean just after, I mean just few minutes. there are lots of things that could cause the status not being showing correctly, like network, etc. that is outside ConfigMgr, but in this post, lets talk about the main one, state messages. When using SCCM 2012/2012 R2, the default detailed level setting when deployment a software update group is to report only success and errors messages. this is quite ok for most environments where you go to the deployment node and check things from there, but you’ll not get the compliance for each update. there are 3 options: all messages, only errors messages and the default one…

Why IT leaders fail to get what they want

IT represents an increasing share of companies’ budgets and head counts. Yet, it still fails to communicate effectively with the rest of the business to align strategies and goals. The main reason for that is that IT leaders usually have a strong technical background. The technical background is critical to the leader’s influence on his team, but introduces a communication challenge with other areas of the business. Today I received this video from a CEO of a company. She can understand it, but told me I would not. She is right by the way! That is how she feels when the IT people from her company tries to communicate something IT is doing. IT fails to communicate with other areas to put their points across. IT Leaders have to communicate with the business in a “common language” and must articulate the message so any human can understand. This is the…

SCCM-Windows Update 6.2.x on Windows 10?

Hi All, I have been reviewing a report I did for a customer where all Windows 10 machines were reporting Windows Update Agent 6.2.x. what caused my customer to send few people on few windows 10 machines and try to troubleshoot windows update issues where it did not exist. of course, after couple of hours/day, they realise this was a data issue instead of their environment issue. When I started to review, I looked at my lab and I had the same. Executing a query on fn_rbac_UpdateScanStatus, I saw all my windows 10 machines also reporting Windows Update Agent 6.2.x So something was wrong. but why? 1st step was to check if the files on the client where the correct version. if you want to know where I discovered which file to look, click here. As you can see, the file was with the windows 10 version…so I checked Powershell…

1E After Work – Let’s talk about Windows 10

Hi All, Are you interested at all in Windows 10? if Yes, this is your chance. Let’s talk about Windows 10 on 26/November/2015 from 18:45 to 21:00. So, join us for the first ever 1E After Work, an opportunity to socialise with peers and industry experts at a relaxed and unique networking event. David Nudelman and I are going to be talking about Windows 10, answering your question, focusing on Deployment and usage on the Enterprise world. I hope I’ll see you there. Register now, limited seats available.

MVP Summit – Hackaton

Hi All, during the MVP Summit, we had a nice work with the Product Team where the MVP group asked some features to be added to the product and that could be coded in a Week and that may be added to the project in a later version (as we hope those will make it) I have to say that we had great projects, in total 10 projects led by MVP’s and coded by Microsoft… Team 1 – Active Have you ever needed to know what machines are active? you need this, they delivered a way to see what machines are online, they integrated with Cortana and etc. I have to say, really great project Team 2 – Wizards Have you ever used the console to do stuff and needed to select the same option over and over? this is the “fix”. It will allow you to save the options…

SCCM-Compliance Setting Script error 0x87d00321

Hi All, When working with Compliance Settings, I normally end up using scripts and often, I get the error 0x87d00321. If you use CMTrace, you’ll see that the error is: The script execution has timed out. Source: System Center Configuration Manager —– Now, we need to understand how it works and how to change. The script timeout information is saved under the class SMS_SCI_ClientComp, Component Name Configuration Management Agent on a lazy property called ScriptExecutionTimeout. The default values is 60, it means that the script will be timed out after 60 seconds of execution. The value, can be seen when using the following powershell script  

  Now the trick part, how to change? As you can imagine, not that trick if you have PowerShell. The script below changes the default 60 seconds to 600 seconds,  

  if you want this behaviour to be changed or have…