Tag: Job

RTFM!

Today I had the simplest of tasks to do. Make some software available for some users.
I always test out the software first to see if there are any issues etc.
I was given a CD with a piece of software on it, a single exe with a Username and Password to run it.
That didn’t work? After several attempts, I paid a bit more attention and realised that the Username and Password details were printed in reverse. I skim read the CD and see that it said Username and Password but didn’t notice they were the wrong way around!
So I swapped the Username and Password around and tried it again. Still no joy!

I left it for a bit as I had other stuff do and came back to it just before lunch.
I had a quick read of the manual and that told me a Username and Password combination the same as what was on the CD but the other way around! However, I had already tried it both ways!

I copied the exe onto my desktop and popped the CD out of the drive and run the program again making sure that I had typed the password in correctly. This time it worked? WTAF?
I then put the CD back in and tried it again only to get the same error as before?
I then loaded up the manual to have another read only to find a sentence saying that you have to copy the exe onto your computer for it to work? Err I guess I must have missed that bit. Ooopps!

Being an IT Pro! I never read the manual 😉 maybe I should try that from now on!

Unable to join the domain?

Today I set about installing a new server to replace an old one. This was going to be a Virtual Server on our Hyper-V cluster.

I have built enough servers of varying OS versions on Hyper-V enough times to not even think about what I am doing so was a tad surprised when it failed to join the domain.
A quick check of everything showed nothing obvious, as sometime I do make the odd stupid mistake!
The server had a DHCP IP address, I could ping IPs on the network, I was able to download files from the internet – which were about all I normally do before joining a new server onto the domain.
I let the server update itself with the latest OS updates and reboot, but that made no difference.
I then set about checking out the NetSetup.log and work through any issues in there.
After checking that and getting nowhere and starting to lose interest I decided to move the VM to a different node and try and add it to the domain again. This time it worked!

I really have no idea what that is as I have not had that issue before and have joined servers on to the domain with not issues plenty of times.
Maybe if I have a lull in work I will revisit, but as I have looooaads to do I don’t think that will happen anytime soon.

Dodgy Recruitment – Update

Today i received a message on my website, interestingly from someone kind of detailed in one of my blog posts.

The blog post was Dodgy Recruitment which detailed my issues trying to get my details removed from a recruitment company that i never signed up with or wanted any information from.

It was a ridiculous trail of just how stupid things can get and just how much some of these people do not care about peoples personal data.

The message i received was polite and asked me if i could remove my blog post, as it have been over 2 years since it happened and that working practices had changed to put a stop to the issues i had experienced. Apparently my post was finding its way to the top of a search engine – number 2 on Google by the looks of it. While it was good to hear there had been changes, i want the original post to serve as a warning, after all once my email address get used and abused i stand no chance in getting it removed.

QuickTime Issues – Poxy Apple Software

What a waste of 3 days this has been!

A problem was reported to me – someone couldn’t view a webpage with a QuickTime move in it.
Given that QuickTime was in need of an update as it was well out of date, I decided to update it first.

I am really not sure what the hell was going on, but it was plagued with errors. The main one being when I created the deployment package in SCCM it deployed the Apple Application Support MSI but then failed deploying the QuickTime MSI. The Apple Application Support MSI was a dependency of the QuickTime MSI. That worked fine but the QuickTime MSI failed saying that a version of QuickTime was already installed.
So I deployed a clean image to my test machine that included QuickTime and set about deploying the new version of QuickTime. Same error again – a version of QuickTime was detected again. Ok so much for upgrade! So I removed all Apple components and deployed QuickTime again. The same error.
I double checked and went through the registry and removed every Apple reference, went through ProgramData and removed everything Apple and in Program Files and Common Files etc. With everything gone I deployed it again. The same error?!?!

I then decided to run the MSI files manually. The Apple Application Support installed fine, but the QuickTime failed again with the same error.
This time I ran SysInternals Process Monitor to capture everything so I could see what was going on.

Several hours later I came across a registry entry that looked like it was causing the error. I deleted it and run the QuickTime MSI again only to find the registry key was back and so was the error. Now that made no bloody sense at all?
Thankfully I had a weekend to forget about that crap and start a fresh on Monday, which seemed to work as I redone the 2 deployments in SCCM and it then installed Apple Application Support and QuickTime with no issues. I really do not know what happened there, as nothing was different.

So, back to the original reason for doing this, I checked the online video and it still didn’t play.
So after all that faffing I was no further forward!
I then renamed my roaming profile and logged in and tried it again. This time it worked!
I looked through the roaming profiles folder to see what Apple stuff I could find, but as I severely limit what is allowed to roam there was no Apple files / folders there.
I then coped the old registry file over and logged on again – movie didn’t play again.

So the issue was with the registry.
I loaded up regedit and went through all the references to Apple or Quicktime that I could find, deleting all then one at a time then trying the online video again.
I finally came across a key called

HKCU/Software/Microsoft/Internet Explorer/Internet/Registry/REGISTRY/USER
[SID]/SOFTWARE/Apple Computer, Inc./QuickTime/LocalUserPreferences

With a setting called FolderPath that was set to an invalid location.
I changed the location to a valid one and hey presto it worked! FFS

It’s so nice to see Apple software that is enterprise friendly!

Recovery again – win some, lose one

Today I got given a USB key stick to try and recover data off.

I tried my trusty recovery tools and was greeted with a stat that wasn’t going to work out too well!

It took 50 mins to scan 3 sectors on the key stick and given that there were 31015 sectors reported in total it was not feasible to carry on

31015 / 3 * 50 / 60 / 24 = 358.97 Days!!

Hmm I think not. I know I spend a lot of my time sat around waiting for progress bars, but that is one progress bar that I do not want to wait for.

All that was left was to deliver the bad news to the owner!

I state what I always say yet again – Do not rely on a USB key stick to hold your important data and expect it to work everywhere all the time, because you have just learnt the hard way what can happen. Back it up and back up your backup, and if you are that worried, backup the backup of the backup! And by that I do not mean on the same key stick or hard drive.

SCCM upgrade from 2012 SP1 to 2012 R2 + CU

So, finally I have finished upgrading all of our clients to the latest version and CU of the SCCM client.

To say it has been a challenge is an understatement.

You would think that given what SCCM is used for that it would be easy and quick to do, but no.

There were just over 400 machines and once I upgraded the server form SP1 to R2 and then updated it to the latest CU I had to deploy the R2 client and then deploy the update to CU4.

The R2 client seemed to get deployed quiet easy, there were a few machines that for some reason had really really old SP1 version on them. For those, there were a few that didn’t like the upgrade, so I had to uninstall the old client and then deploy the new one.

I then set about deploying the CU4 update to all machines. There was a bunch that wouldn’t update, no matter how long I left it and no matter how many times I forced an Application Deployment Evaluation Cycle it stayed on the old version.

I had a SQL query listing all the machines on the old version, the started off about 49.

I found it easier to remote on and manually uninstall the client, wait for all processes to terminate, rename the old SCCM directory and then reboot the machine. I figured that out after a bit of trial and error trying to get things off and on again!

So, thinking I had it sussed out, I was somewhat surprised when I refreshed my query one morning to find the number of machines had increased. Looking closer it was a few machines from the Labs.

RDPing on showed that the version was indeed the old version. I really couldn’t be bothered to see what the hell was going on as it had been a good few weeks that I had been trying to do this and people not logging off! and machines in locked rooms that didn’t work with WOL were doing my nut in.

So for each of those I applied my fix – remove the old client, wait for processes to terminate, rename the old CCM directory, reboot the machine, deploy the new client via SCCM and then deploy the update. That seemed to work for every computer that somehow managed to downgrade its client version on a reboot!?

Now to package and deploy the growing list of application updated that are needed.

A name from the past!!!

Today I got a call from someone that I do work for / help out / rescue now and then asking me some technical questions.

Not really that difficult to answer and in theory put into effect, but with that came the news that it was for someone that I thought I had heard the last of, or at least never have to deal with again!

Now I’m a the middle of a dilemma, do I help out a friend that has been good to me, as I have to him, or do I tell him I won’t do it. I always try and be professional when it comes to my reputation and working with other people. Unfortunately the more I thought about it the worse it made me feel, all the thoughts and feeling came back along with a lot more hatred for the person and the situation they caused and put me through. I have enough stuff going on in my head to deal with at the moment without adding that to the mix!

I think the best way for me to go with this is to do the job if/when it comes up, with the conditions that I do not have to deal with the person in any direct way and keep my contact details well and truly private.

Shit, I hate being put in situations like this!

Another hard disk for recovery

It’s happened again, someone else has asked me to take a look at a hard disk that has lost all its data.

I was hoping that I wouldn’t see one for a while after the last one, but it appears not.

It really does amaze me what people keep on a portable device that is highly important and impossible to get back.

Anyway, I recovered what data was on there, took a few hours to do, but most of it was there. Sods Law says that the first file that was needed was one that it hadn’t manage to recover!

I convinced the user to put anything that was important up in the cloud so that it was safe and could be got at easy. Is always nice to see someone taking on board some advice.

A reinstall?

Today I heard the words that I dread hearing, especially coming from someone with a technical back ground.

While looking to fix a problem, a problem that seemed to point to a few things as the cause, I heard `if I can’t fix it I will reinstall it`.

To me a reinstall of a computer is the last thing that should be done, and from experience it is only as a result of unexpected damage that is has to be done – like a hard drive failure that corrupts too many files, or as a result of someone getting impatient with Windows Updates and turning the machine off when it says not to! why would you do that?

So, I volunteered to take a look before the reinstall was started and had fixed the problem within a few minutes.

After I returned the computer, I sat and pondered on the thought processes involved in making the decision to reinstall……