Not all computers work better with hardware acceleration, especially those with incompatible drivers.
A couple of users contacted me asking about “white screens” and freezes in Outlook 2013. The simple solution is to disable the hardware acceleration…
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.
My customer has bought a Hewlett-Packard server with a Windows Server 2012 ROK (Reseller Option Kit) license.
However this customer had some issues with the installation of the license on the Hyper-V guest server. Since the Windows server does not recognize the ‘hardware’ as a Proliant server, licensing will not succeed.
However there is a simple solution…
I was faced with an issue regarding NOD32 today. A couple of clients had an old (undocumented) configuration of their antivirus.
As it turned out the clients had “Protected setup” which means you cannot access the settings, or un/reinstall the program without a specific password. It also happened to not be set up to talk to the appropriate “Remote Administrations-server”.
I have been struggling a bit with adding .NET Framework 3.5 on a few systems (and reference image for MDT).
The posts on MSDN and TechNet are good, but not always crystal clear.
Here is how I solved the issues we were experiencing…
I know many IT folk have been waiting for the updated Administrative Templates for Update 1 to ensure a smooth rollout…
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 several reasons to change the default organizational unit of computers that join the domain.
The default OU (domain.local\Computers) cannot be linked with GPOs, and should be avoided since its builtin.