Wednesday, 13 March 2013

Windows 2008 R2, deleting Deployed printers

If you open print manager and see a printer that's been deployed but thats not in use - you need to do the following to delete it.

Open GP Manager - goto the specific GPO and delete the printer from there - mine was in -


Windows Server 2008 R2 - printer FLOP-UP

Ok, so briefly what happend was one of my printers "fell" off the network it seemed. I then found I could ping it, connect to its webpage and do whatever to it but not print to it. Reboots, cold starts didnt help.

I deleted any .spl files in the c:\windows\system32\spool\

So I checked my Server - I removed the printer, reinstalled it and tried printing. Still didn't work.

I tried a different printer driver and tried printing - Now I got into a situation where my print spooler on my Server stopped everytime you trried printing to the printer in question. Little research and a chat with a buddy confirmed print spooler corruption.

On my windows 7 client I got no access to any printers, if you wanna print you get a box asking you to please install a printer... Normally a System Restore fixes this issue.
What helps? Delete the printer and reboot. Then re-add the printer.

PS: please do not use weird characters, - or / or \ in your printer names theres a bug in Win2008R2

Errors I got:



Wednesday, 20 February 2013

Reset MacMini Admin Pwd


To reset your OS X password without an OS X CD you need to enter terminal and create a new admin account:
  1. Reboot
  2. Hold apple + s down after you hear the chime.
  3. When you get text prompt enter in these terminal commands to create a brand new admin account (hitting return after each line):
    • mount -uw /
    • rm /var/db/.AppleSetupDone
    • shutdown -h now
  4. After rebooting you should have a brand new admin account. When you login as the new admin you can simply delete the old one and you’re good to go again!

Tuesday, 19 February 2013

Event ID: 12294

Event ID:

Event Type: Error
Event Source: SAM
Event Category: None
Event ID: 12294
Date: 3/3/2003
Time: 9:42:55 AM
User: (USERNAME)
Computer: (COMPUTERNAME)
Description:
The SAM database was unable to lockout the account of ? due to a resource error, such as a hard disk write failure (the specific error code is in the error data) .  Accounts are locked after a certain number of bad passwords are provided so please  consider resetting the password of the account mentioned above.

Found one PC trying to reconnect to this Server (Below) and I get the event ID (above)

The computer BLOSSOM tried to connect to the server \\AISCTSRV02 using the trust relationship established by the AISCT domain. However, the computer lost the correct security identifier (SID) when the domain was reconfigured. Reestablish the trust relationship.

Friday, 2 November 2012

Add repository to ubuntu

sudo: add-apt-repository: command not found

If this happens, you must first install python-software-properties, which contains the add-apt-repository command. 

To do so enter the following:

sudo apt-get install python-software-properties

Tuesday, 3 April 2012

8ta 2GB+1GB using Vodaphone ZTE K3805-Z USB Modem

I've got a ZTE Vodaphone USB Modem that I'm going to use with my 3G network instead of paying R400 or some places charge R600 for a generic USB Modem.

I didn't want to be bothered to flash the USB Modem and its too lenghty a process so all I did was:

1. Topped up the 8ta simcard to the 3GB+1GB Deal (popped it into another phone and followed the prompts - you have to have the "3GB+1GB" deal attached to your simcard as it wont work on all 8ta sims)
2. Put the simcard into the USB modem
3. Install the Vodaphone software (which above all else installs the USB modem drivers)
4. Select the 8ta network from "my network connections" once the modem have been installed

My current 8ta network is "655002".

Works a charm..........

Monday, 26 March 2012

Nagios 3.3.1 bug - Host stuck in scheduled down time
















Setup
Ubuntu: 10.04.4
Nagios: 3.3.1
Plugins 1.4.14

Host scheduled for downtime but downtime have exceeded and host is still stuck in downtime.
Unable to get host out of the downtime

RESOLUTION

Remove Host from Nagios complete, do a reboot, recreate host - this was the only way I could get my host from being stuck in a downtime situation.