Wednesday, April 02, 2008, 20:10

Wow! It's been a long time...

Has it really been almost a year since I updated this?

Well, I've started development on ManagePC again and this time it's going to be a big one. The whole interface is going to change to give it a more professional XP look (similar to Hyena and Everest, two commercial tools).

A bit like this http://www.lavalys.com/products/whatsnew/core2_en.png

I'm also going to optimise the code more now that I have a colleague who is something of a .NET expert ;)

There's loads of stuff I'd like to add such as reporting and SQL DB support but the main priority now is too get the new interface up and running and optimise the existing code.

I'll have to go all Duke Nukem Forever on you and say it'll be done "when it's done". Hopefully you won't have to wait another 9 months though!

[ No comments ]

Wednesday, July 18, 2007, 11:17

WMI really can be very annoying..........

I have finally established what was causing these errors when running on servers (either Win2k or Win2k3). It's partly my fault and partly Microsoft's (well, I'm going to blame them anyway!). The problem stems from the fact that when running WMI queries for a lower OS version to a higher one (e.g. Win2k to XP) you need to change the WMI Authentication Level from the default of CONNECT to PACKET. I was doing that but was saying, effectively, "if we're not running on XP, assume it's a lower OS version". So, people running on Win2k3 were using a different Authentication level. Now, that SHOULDN'T make a difference when querying an XP box but, for some reason, it caused this strange error.

Anyway, that's fixed now and I have even tested it on a Win2K AND a Win2k3 machine. I'm just awaiting word from someone that everything works and then I'll upload a new minor release (v 2.41)

[ No comments ]

Tuesday, July 17, 2007, 14:36

Threading errors on Win2K/Win2k3 servers (AGAIN!)

At least one person is still getting errors when running on servers. I can reproduce the error which is a good thing but there is absolutely no reason (as far as I can see) why this should happen only on servers. The code that's failing is perfectly OK and .NET compliant so it must be SOMETHING with the machines themselves. I'm getting the feeling that it's something in the WMI implementation on Win2k/Win2k3 Server that's causing the problem.

[ No comments ]

Thursday, July 12, 2007, 10:22

ManagePC and MWLoggedon new versions coming

I've just sent new versions of ManagePC and MWLoggedon to the webmaster so (hopefully) they should be available soon. I will, of course, send everyone on the mailing list an email when they are there.

For now, here's the changes

ManagePC 2.4 Changelist

Fixed bug that could cause a crash when scanning a machine with large amounts of RAM
Fixed bug that that could cause Services and Processes lists to be empty when using alternate credentials
Fixed bug that could cause crash if return was pressed immediately after scanning a machine
Removed need for Interop.Excel.dll and Interop.ActiveDS.dll files to be present (they're now inside the EXE)
UNTESTED: Vista compatibility. I think that the application should now work on Vista. I've not been able to test it however.

MWLoggedOn 1.10 (BETA) Changelist

New syntax and functoionalities.

mwloggedon \\computername (e.g. mwloggedon SERVER1) - returns the logged on user of SERVER1
mwloggedon [username] (e.g. mwloggedon johndoe) - scans every machine in the domain and determines which machines johndoe is logged on to
mwloggedon -d - scans every machine in the domain and returns the logged on user for that machine

Passing /nolog as an additional parameter will suppress error logging

[ No comments ]

Monday, June 04, 2007, 12:09

WMI Query Builder sources available

On request, I have uploaded the WMI Query Builder sources to the SourceForge page.

[ No comments ]

« 1 2 3 4 5 6 »