Unsolved
This post is more than 5 years old
7 Posts
0
24041
August 12th, 2008 14:00
Install MDSM on 2008 Server Core?
Greetings, all. I'm planning to update some PE2950 systems connected to an MD3000 from Windows Server 2003 to 2008 Server Core.
I've downloaded the latest MD3000 resource CD (MD3000CD15.iso) and read the installation guide, which says to run setup.bat on Core systems. When I do this, the prereq check passes and I get a menu of the readme, install SAS 5/E driver and install storage software. I choose Install MD3000 Storage Software and get a language selection screen. After hitting OK for English I get "Installer User Interface Mode Not Supported" "Unable to load and to prepare the installer in GUI mode."
While the docs don't talk about Core much they definitely state that it is possible to install MDSM. Help?
Perhaps someone knows the command line switches for SMIA-WS32-02.71.36.09.exe to perform a quiet "Host" installation?
Cheers.
Dev Mgr
6 Operator
•
9.3K Posts
0
August 12th, 2008 15:00
How far did the online install guide <ADMIN NOTE: Broken link has been removed from this post by Dell> get you?
dddugan
7 Posts
0
August 12th, 2008 16:00
Not terribly far. Under the 'Installing on Windows Systems' heading i run setup.bat as instructed. Following on to 'Host Installation' I skipped the driver installation (step 1) and went to 'Install MD3000 Storage Software' (step 2). I see an InstallAnywhere preparing for setup progress bar count to 100%, then a language selection screen. English is the default selected, I hit OK and immediately get the UI error.
Cheers.
Dev Mgr
6 Operator
•
9.3K Posts
0
August 12th, 2008 16:00
Dell-Jeff G
156 Posts
0
August 12th, 2008 19:00
Here's a couple of things to try...
People have also seen this error with InstallAnywhere when they have special characters in their username like ! or #. If this is the case, they can create a temporary username and then install.
This could be because the user does not have admin rights or the user does not have the temp environment variable set properly. This could also be a problem if the temp variable ends up with special characters due to a special character in the username. Changing the temp environment variable to something like “C:\Windows\Temp” should also fix that. This can be done using the Set command
dddugan
7 Posts
0
August 12th, 2008 21:00
Nice one, Jeff. The account I was using did have a ! in it. Using an account with no special characters worked fine. Don't recall having this issue before, but may have used the local administrator account then.
Working fine now -- thanks!
Dell-Jeff G
156 Posts
0
August 12th, 2008 21:00
I can't take all the credit. smileyhappy:
The person I asked actually googled it and came up with the possible solutions.
Glad to help.