Welcome to the Jocha blog!
I received an inquiry from one of my mid-size (100-200 users) customers today. They’ve been planning on implementing a new online service which requires the latest Java version.
The clients have a large quantity of outdated versions of Java, which needed to be uninstalled before we deployed the newest version.
They are currently running Windows 7 and Windows 8, so somewhat modern operative systems.
We have been working on migrating a customer from Windows 7 over to Windows 10. Our goal is to have Windows 8 and 10 clients pull the pictures from Active Directory to the users local profiles.
Do you ever get that sinking feeling, when you’ve forgotten the root password to your test lab? Again?
I hate it too! So I decided to figure out a way around it, using a work around…
I finally I got some time to play with the new Azure Active Directory Sync tool and its configuration.
The installation was very straight forward. The step-by-step instruction are provided on MSDN. The administration tools and scripts are located in difference places compared to DirSync which was little confusing in the beginning.
A customer of mine recently started deploying Windows 8 in their environment. MDT was set up and the deployment was working fine, but after deployment the Windows 8 machines wouldn’t connect to the WSUS server.
When trying to connect to the WSUS-server through the Control Panel I got an error message.
There are numerous of ways to measure update compliance in an enterprise. Some prefer to just compare the compliance of a Software Update Group against a collection. The issue I’ve found with this is that when you release updates the compliance falls down to 0%…
This article focuses on the scenario where the laptop/desktop has been lost or stolen, and how to make sure that the local data/credentials are secured/encrypted.
I created a powershell-script which will reset the password of all users in a specific Organizational Unit.
I prefer to set unique high-end passwords for all users. If you prefer a more ‘user friendly’ approach simply…
A downside with the ADMX files is that when you update them, and the new files replace settings and values you end up with orphaned settings in your GPOs. In our example we had two orphaned registry values from a previous OneDrive ADMX.
We’ve been upgrading a customers environment… for one of their workstation configurations they didn’t want the computers to lock on idle, which is enforced by default.
Back in 2012 I wrote an article about dynamically setting a computer name during a Task Sequence. Here is my updated and improved script. I’m currently setting up a deployment solution running SCCM with MDT 2013…
There are a few different approaches when it comes to cleaning up the Windows 10 deployment. I prefer to uninstall the built-in applications which my enterprise and customers have no need for.
Jocha previously released a very popular mail report-script for Windows Backup. A downside with the new Azure backup-agent is that it did not offer mail reports… until today!