|
Mar 18 |
HP Driver Clean-up Utility ntScrubber
Posted by Philip Elder on 18 March 2014 11:14 AM
|
|
Original Posted Here: MPECS Inc. Blog: HP Driver Clean-up Utility NTScrubber If there are any problems with HP drivers then the ntScrubber utility is the one to use.
The utility will completely remove any remnants of HP’s driver set on a machine. Once rebooted one can then work towards installing the printer or printers again. Philip Elder Chef de partie in the SMBKitchen ASP Project Read more » | |
|
Feb 25 |
Adobe Reader and Acrobat – Content Preparation Progress: Please wait while the document is being prepared for…
Posted by Philip Elder on 25 February 2014 09:56 PM
|
|
We have a client that is being bugged by this prompt when opening certain PDF files.
Adobe has a KB article on this: The solution is to do the following:
The dialogue has to do with accessibility. Philip Elder Chef de partie in the SMBKitchen Read more » | |
|
Feb 5 |
CaseWare Working Papers Error: Printer not activated, error code -30
Posted by Philip Elder on 05 February 2014 12:27 PM
|
|
We are seeing CaseWare Working Papers choke on a PDF Batch run with the following error:
CaseWare has a KB on the issue: Printer issues with Windows 8.1. Though in our case the OS is Windows 7 Enterprise x64 with the indicated update (2014.00.072) having already been applied to all systems. As per the KB article we took a look into the registry with the key mentioned missing completely:
The affected systems have the printer though:
Our steps to get things going:
We will now see a successful run of the batch:
Once that process has completed have a look at the registry key we created:
We are not 100% convinced that this is a “fix” or a workaround as things have been operating normally until just the other day. Philip Elder Chef de partie in the SMBKitchen Read more » | |
|
Jan 2 |
RD Gateway and RemoteApp Error: Remote Desktop can’t connect to the remote computer "RDS.Domain.Local" for one of these reasons:
Posted by Philip Elder on 02 January 2014 07:17 PM
|
|
We just finished setting up a Windows Server 2012 R2 Standard RDS server and began testing the RD Gateway, RDWeb, and RemoteApp features and hit this:
The third reason is out while the first two are not applicable since our access policies are set up correctly. Our search brought us to: Following Solution 1 we puzzled about trying to figure out where the NPS thing was! Click on NAP in Server Manager and then right click on the server name. Choose Network Policy Server in the menu. Once the NPS console comes up right click on the root node NPS (Local) and click Register server in Active Directory.
Click OK twice and then test again.
Good to go! Philip Elder Chef de partie in the SMBKitchen Read more » | |
|
Nov 25 |
Troubleshooting ShadowProtect Backup Failure 503 Fatal I/O Error
Posted by Philip Elder on 25 November 2013 12:08 PM
|
|
We have one SBS 2008 riding on a cluster that has started to fail its full backups but only at certain times. The KB indicates that the problem is resident on the source if the error falls on a read or on the destination if on a write. In this case our failure was on a write so we started to focus in on the destination. For this cluster setup we have the backups stream across the wire to the standalone DC on an HP MicroServer that was also protected by ShadowProtect. We looked into network connectivity as well as for disk I/O errors in the Event Logs with no results. The last place to look was in the ShadowProtect setup on the DC itself. Sure enough, the DC was set to run an incremental close to the same time the one backup on the SBS VM was failing. We changed the standalone DC backup schedule to run one incremental at night to avoid any further conflicts with the VM backups that were streaming to it. We now had a successful backup set on the SBS VM. Philip Elder Chef de partie in the SMBKitchen Read more » | |
|
Oct 7 |
Hyper-V Cluster: An error occurred while creating the cluster: Unknown error (0xc0000133)
Posted by Reprinted Article on 07 October 2013 12:22 PM
|
|
We had just finished walking through all of the steps to set up two nodes for a Server 2012 RTM Hyper-V cluster when we got hit with the following error:
Our initial searches turned up very little when we included Hyper-V and Cluster in our terms. The error code however turned up a tie into time synchronization. These nodes were set up using Windows Server 2012 Standard in Server Core mode. And, we had missed step 9 in SConfig: Date & Time! The time zone was incorrect on both nodes. We also noticed that the time on the test network was about 9 minutes out from our own. So, we had missed configuring the time service on the physical DC to poll the Canadian pool.ntp.org servers.
Once we had the domain time in order and the nodes synchronized to the DC we were able to successfully stand up the cluster in Failover Cluster Management.
In the end not referring to our process manuals was the key. ;) Philip Elder Chef de partie in the SMBKitchen Read more » | |
