lol, alright thanks for your help with this, I appreciate you putting this out. I sort of have an idea of how it works .. I was running it from my desktop as administrator. Can it not detect 2010 VL if it's not installed to C:\?
I actually don't know? Just uninstall and re-install on C:\ Reboot between uninstall/install Use cody's toolkit to uninstall Then it will work fine
This is about Windows Small Business Server 2011 Essentials Wow timesurfer! This is most definitely a well supported solution! Thanks! First of all, your "adjustments for EditionID = ServerSolution," SBS 2011 Essentials MOD Trilogy works great! I just did the regular IR5 install and haven't tried the MPC. Thanks for making the needed mods to your code. I compared the "OEM Trilogy 3.7" and the "SBS 2011 Essentials MOD Trilogy" using WINMERGE. For my understanding, is the "ServerSolution" key used in the OEM Trilogy geared to support WHS 2011? Thanks again for your rapid assistance!
Windows Small Business Server 2011 Essentials I think I'm getting it now, timesurfer. At the very basic level, I don't really need to climb into all the code, I'm just very happy that it works! However, it can be useful to have a rudimentary understanding so that I can ask semi-intelligent questions if--down the road--problems emerge. So let me see if I can ask a better question. Prior to providing you with the new "ServerSolution" SBS Essentials "VVWPG" key, you were using a"Y7GVM" key. To what OS was the old "Y7GVM" key supposed to apply? I ask this since with the new Trilogy code the "Y7GVM" key no longer exists. And finally, an FYI. I forgot to mention that before applying your solution, SBS Essentials gave you 3 rearms of 60 day grace periods. After applying your solution, you now get 5 rearms of 60 days or 300 days of trail usage!. Pretty cool, huh?!
First Trilogy 3.8 will be reflection of latest changes SBS11 Second I found all these default keys about a year ago and MD and myself implemented them so maybe that key is from prior version for SBS I have no servers so I'm uncertain the dashboard or nag situation I am glad it worked for you
No chance whatsoever ...lol Content is perfect IR5/MPC = 100% successful IORRT = 100% successful ACS5T = 100% successful
Very nice tool. However, in 3.7 I had to use the MPC. The 'C:IR5' command would not work. Was that fixed in 3.8?
I don't believe there are any changes between 3.7 and 3.8 that would cause IR5 to stop working. The main reason that IR5 does not work on your system has to do with how your system is setup (partitioning is usually the main cause). When IR5 does not work, you should use MPC (as you did). Timesurfer included MPC for those of us that try IR5 and it does not work. The main thing is that, regardless of whether you use IR5 or MPC, it works in the end.
Basically tomah summed it up but the only reason IR5 did not work was because of RE bug that changes drive letter name What drive did it say in Recovery console? I'm guessing for 97% of people IR5 works fine Thanks for the comment
Hello Timesurfer, I used your IR5 script for over a year without problems in a office PC, but 2 days ago it stopped working and I don't understand why. The script ALWAYS report "Right click Trilogy and run as administrator" but I run the script as administrator !! This is the part of the script that seems do not work properly The %windir%\TrilogyAdminTest folder was created, but the errorlevel check seems locked on >0 and the command rd %windir%\TrilogyAdminTest is not executed Any ideas?
Alright thanks. I don't remember what it exactly said, but it went along these lines: 'C:IR5' is an invalid command. Maybe my drive letter changed in RE? Never the less, the MPC worked, and you have saved me
You'll have to remember all the changes or whatever you did that caused that otherwise Trilogy is working fine especially if it did before...lol I believe I said drive letter changes in RE cause ther is RE bug