ben.hamilton.id.au

Enjoyed reading this article suggesting ways to use LinkedIn, especially numbers 1, 7 & 8.

Re: #1 – I think it is important to fill in plenty of detail on LinkedIn – if I visit your LinkedIn profile and find that I can’t get to know you better then it has failed for you. By telling me (or telling a potential client/employer) more about yourself can only be a good thing.

Re: #7 & #8 – I’m going to work on these two over the next couple of weeks…

Do you love your job? I do. Let me tell you why. I get to change ‘someones’ world on a daily basis. And I love it. 

I do technical support for a small marketing firm, all of our clients use ACT!, which is a contact management application. When you show someone how they can improve their productivity, improve their bottom line they get excited, and by extenstion, so do I. 

Just this week we demo’ed a customisation that will totally change the clients ability to track the jobs they do, the items associated with those jobs, the people and all the rest of it. The client was literally getting out of his chair, walking around “of course”, “WOW!”, “does that mean…” – “yes it does”. It was a the HIGHLIGHT of my week. To have spent the time delving into their business to work out what they do, how they do it so as to figure out what they needed was fun, it was truely enjoyable, but to see the reaction, the excitement, the realisations for what would now be possible – that was GOLD.

I love my job.

[note: the title "Changing the world one ACT at a time!" is a hat tip to an insightful guy with a Blue Monster]

[note: edited to fix a typo and add URL for www.evolutionmarketing.com.au]

A client has a SharePoint installation that has died, with all their project files and data in it.

In the course of searching for how to resurrect it, I’ve found the following that seem to be things that others may well benefit from:

• An article on the Official SBS Blog, pointing to an unofficial tool:

  During disaster recovery, if no backups other than the database files exist, we may manually extract the files from the database as a “belt and suspenders” approach to disaster recovery.

• A script from Mark Jen at Plaxo that restores files from SharePoint SQL DB with their directory structure
• An article from Ed Walters on how to backup SharePoint

Possibly the biggest lesson here is to ensure that if your using SharePoint, make sure you back it up PROPERLY, ALL OF IT.

If like me you need to test if network traffic is getting through a firewall then this tool will be of use to you as well.

You run it on the target/client system, specify which port you want it to listen on, a response message and click on listen. Able to listen on multiple ports even.

Get listen from here.

Well. Didn’t expect to see this, but here it is, the RFCs regarding SMTP have been updated. (hat tip)

Makes for an interesting read if your into this kind of thing.

Sometimes while supporting products, it is very useful to know just what version/s of .NET are installed.

Found this tool just now shows you just that: Free DotNet VersionCheck Utility

If you’ve ever wanted a quick way to find out which versions and service packs of the .NET runtime are installed on a machine, or if you’re trying to resolve a ‘missing mscoree.dll’ error, then DotNET Version Checker is for you. VersionCheck itself does not depend on the .NET runtime. VersionCheck will also tell you whether you have the required Windows components to run .NET applications, and will prompt you with download locations if not.

Update: this page at Microsoft lists the downloads for .NET in the left menu bar.

Spotted this great list of open source tools for system administrators: 24 Great Open Source Apps for Admins & Technicians.

I can personally vouch for a number of these:

• Angry IP Scanner
• PuTTY
• DBAN
• DeltaCopy

For some tools that are not open source but free, you can’t go past live.sysinternals.com (details here) – now owned by Microsoft themselves these tools make a Windows Sysadmin job much easier.

A Terminal Server I was attempting to work on today gave quite a lot of grief. The first hint was that users were unable to login to it. When I then tried to login, it gave an error message of: Login Failed
You are connected to the remote computer. Howerver, an error occured while an initial user program was starting, so you are being logged off. Contact the system administrator for assistance.

So I rebooted it remotely using the command shutdown /r /f /m \TSERVER1 while having a continuous ping running, from the ping results I could see it go down, come back up. However on trying to login now, after entering a username/password I could see the logon script run, but no taskbar, start button appeared. Right clicking the desktop didn’t give any menu.

I could however navigate to the hard drive on that machine by pointing My Computer to \tserver1\c$\.

Copying some of the tools at live.sysinternals.com I was able to view the event logs, no issues apparent, check status of various services, all ok.

So I connected via RDP once more (mstsc /v:tserver1 /console) and viewed the background (still no start button or taskbar) and pressed CTRL-ALT-END which allowed me to start the Task Manager. This allowed me to run a new task (File | New tas (run...)) so now I was able to copy the sysinternals autoruns program to the root of the C: partition, and run it from the affected terminal server. Running c:\windows\explorer.exe didn’t work tho.

Delving into it’s depths I found an entry for HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\Explorer – renaming this entry then allowed Explorer to run. So I’ve exported the key (in case I do want it sometime) and then deleted it.

Rebooted the server once more and bingo, it lets everyone log in. Very satisfying after a couple of hours of mad hair tearing.

Like Symantec Anti-virus. At a friends house right now, and trying to uninstall the product, it won’t – it keeps saying that something else wants to keep it there. Very unhelpful error message by they way (if Symantec is listening).

Found a great page that explains how to remove unwanted software (surprise, they also trying to remove Symantec… hmmm….).

Here it is at it.toolbox.com/blogs/locutus.

In a nutshell this is how:

1. Open regedit, browse to HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\ WINDOWS\CURRENT VERSION\UNINSTALL
2. Then do a search for Symantec (or the name of the software you want to be rid of)
3. Copy the value of UninstallString
4. Open a command prompt (Start | Run | CMD) and paste the UninstallString here and add REMOVE=ALL to the end of that string, press enter. It will look similar to this: MsiExec.exe /X{DBA4DB9D-EE51-4944-A419-98AB1F1249C8} REMOVE=ALL
5. Done.

A common grumble I hear about the place is that the internet is too slow. While many things on the local LAN can affect this, the first port of call is to actually know what size pipe we have to the internet.

To determine this, Speedtest.net is great. It shows with good use of eye candy how quick your upload and download speed is (or isn’t).

Not only that but it identifies which ISP your using. A quick handy tool to use.