I tried miniadmin1.25, 1.20 and although I have stopped all services it either creates and doesn't work in Win 7 (v1.25) or it fails to complete after an hour or more (v1.20) why?
can you post the log files here so we can see what it's adding? Mostly this is because you've stored things in the sbadmin folder which are not expected, like extra copies of the db, or the db in a non-standard folder.
The miniadmin1.25 completes with no errors. It just doen't work with our Win 7 Ent. When you launch it you get. 0xe0060001 Unknown Encryption Algorithm. Here is the odd thing. If I put a v524 down first (via a past minadmin install) and then run this install made by miniadmin for v5.2.12, it works fine. I was pretty sure I got everything out of the SbAdmin folder that could affect it. I didn't see anything out of the ordinary and again, it did finish without errors.
It's probably due to the folder shadowing - my guess would be to run it as admin?
Still need the log files to comment more.
Hi Simon, I do run it as an admin. I will run tonight, and get log files. Not sure about folder shadowing, I am the only one connected to box when run. I did have a question, I forget what the option exactly says but it has VISTA in the option. We don't use Vista at all, so should I uncheck that box/option? I have tried running with default setting and checking all options.
Not sure - I don't run W7 so it's never been tried or tested on that platform.
It may be easier just to do the supported thing - install EEM off the distribution media.
While I know we can install from media, when you have over 600 administrators, the chance for folks not installing correctly is a concern. I don't know if they can mess up database by installing the wrong options. It is a two step process, and so if I can just point to a exe to run, it would make my life much easier.
They can always mess up the DB unfortunately - they are administrators after all.
All they need to do is click "cancel" when they get to the create DB step, then they can connect to your existing DB Server.
but, as for getting MiniAdmin running, you might be better off making a package on an alternate OS - Vista or XP for example.
Hi Simon, I am a little confused with last statement. About getting the MiniAdmin running, making package on alt O/S such as Vista, or XP. When I run the miniadmin1.25, I run it within the SbAdmin folder on Windows 2003 server. So could you clarify what you mean? Are you saying just run it on Vista or XP as we are goint to Win 7 and so, not an option. Thanks!
ah - so you are creating the package on W2003, not Win7? That's not clear from your title. You said W7 so I thought you were trying to create on W7.
Sorry - there's not much I can really do to help you, I don't use W7 and have really not updated MiniAdmin for months (if not years). You could probably tweak it though - it's just a HTA.
I imagine you are right that the path structure is different. That can usually be fixed by running "as administrator" though, something that's tricky with HTA's as it's not a right-click option.