Monday, February 25, 2008 4:20 PM
On the connect portal for SCCM SP1 i postet the following "problem":
If you install the SCCM Admin UI on a german windows xp sp2 client and import drivers into sccm, then the driver name is not displayed correctly on the server. On the server the name is the "SCOPEID....". On all other windows xp sp2 computers the name is displayed correctly. Changing the reginal settings on the german client to english does not solve the problem.
In addition if you add a new driver category from the german xp client this category ist not correctly displayed on the server. The server only shows an empty value. Other xp clients shows up the right value.
I have encountered this problem in SCCM RTM/SCCM RTM & ICP1/SCCM SP1 Beta. I have reproduced this behavior in my lab and production environment.
BTW: If you import drivers on the servers sccm admin ui all names are displayed correctly on each client.
The answer from MS is:SCCM doesn't support the MUI (multi-language user interface). If a user creates an object in a specified OS such as JPN, the user must run AdminUI using the same language OS. Otherwise, the user will see the SCOPE_ID instead of the driver name.So if i understand this right it is not possible/supported to add a driver from a german Windows XP client running the admin ui to an english SCCM server even if the german client runs with english reginal settings. (All items in the admin ui on the WinXP client are displayed in english.)It would be great if someone can confirm this behaviour.Best regards,Markus
Tuesday, February 26, 2008 7:39 PMOwner
Sorry it took so long to respond, but I had no knowledge on this specific scenario, so had to ask a dev on it. The response is:
This is expected behavior because the site server and admin console machines are running different locales and provider uses admin console machine locale to convert the driver display name so that the other admin console machines with the same locale will display the names correctly.
However, there is a simple workaround for this issue.
Instead of launching from the Start menu, run the adminui with commandline parameter on his German xp machine:
This will tell provider which is probably on the site server box to use English for the conversion.
Wednesday, February 27, 2008 12:38 PM
Thank you for your answer.
I started the Console with your given command.Code Snippet
"C:\Programme\Microsoft Configuration Manager Console\AdminUI\bin\Adminconsole.msc" /SMS:ProviderLocale=MS\0x409
Thursday, February 28, 2008 4:35 PMOwnerOK, devs are still looking into this. I'll update when we have more data to provide to you on it.
Thursday, February 28, 2008 9:19 PMOwner
In that case, the customer can try a different command switch:
"C:\Programme\Microsoft Configuration Manager Console\AdminUI\bin\Adminconsole.msc" /SMS:Culture=de
The downside of this is that the above Admin console will be English not German, I assume this is ok as he already used the console on the English site server.
Tuesday, March 11, 2008 6:38 PM
So. At first, sorry for my late response!
And now the results:
Trying "C:\Programme\Microsoft Configuration Manager Console\AdminUI\bin\Adminconsole.msc" /SMS:Culture=de
and "C:\Programme\Microsoft Configuration Manager Console\AdminUI\bin\Adminconsole.msc" /SMS:Culture=en on the client and trying "C:\Programme\Microsoft Configuration Manager Console\AdminUI\bin\Adminconsole.msc" /SMS:Culture=de on the server does not solve the display problem.
Tuesday, March 11, 2008 8:01 PM
The correct format for specifying an alternate 'Culture' settings is:
If you do not install the German version of the SCCM console it may still not work correctly; it might work better though; not sure.
Tuesday, March 25, 2008 2:05 PM
On the Client i have tried Adminconsole.msc" /SMS:Culture=en-US and it works for the categories. But the driver name is still displayed as "SCOPEID_..."
Friday, April 09, 2010 4:20 PM
I know that this is an old post, but I too have come across this issue. We have just installed SCCM 2007 R2 and the SP2 update and have found that this is happening.
I was wondering if there has been a resolution to this issue.
Thank you and Kind Regards!!
Thursday, February 03, 2011 1:11 PM
Hello, we are still experiencing the same problem on Dutch windows 7 machines with an SCCM 2007 SP2 R3 console installed. We tried to add /SMS:Culture=nl-BE in the shortcut target.
When we import a driver from the Dutch win7 Admin UI we see in the AdminUI on the SCCM Site server the driver with a name SCOPEID_ ...
Wednesday, April 20, 2011 7:17 AM
We are experiencing the same problems (SCCM 2007 SP2 R3). Starting the adminconsole with option /SMS:Culture=nl-NL does not make any difference.
BUT there seems to be a result with much more impact: The Task Sequence steps Auto Apply Drivers that filter on catagory do NOT work anymore. I tested with an auto apply drivers step that does not filter on catagories, and this one does apply drivers. The filtered steps don't work.
The catagories are blank on Non-dutch MUI machines.
This is a very annoying bug (because the driver catagory filtering now doesn't work, we cannot deploy our machines following best practises of offering only supported drivers).
You know you're an engineer when you have no life and can prove it mathematically
Monday, July 16, 2012 2:27 PM
we got the same problems and fixed them by adding the desired localized information to the LocalizedInformation property array.
we typically use our consoles with an locale id of 1031 (de) and we have the same problems when opening the console directly on our servers (which have an id of 1033 [en])An vb.net example for fixing the display of a certain locale can be found under http://sccmdotnet.blogspot.de/2012/07/fixing-localized-string-issues-in-multi.html
An instance of SMS_Driver would typically have one item in the LocalizedInformation array (which has [in our case] an id of 1031 because it was created with the german console).
By adding another SMS_CI_LocalizedProperties class with the desired locale id to the array, we were able to get rid of the "SCOPEID-Issue".
I'm sure it's completely unsupported but it works fine ^^
- Edited by Schlee, Kevin Thursday, July 19, 2012 10:22 AM
Thursday, February 21, 2013 10:43 AM
instead of doing unsupported things to the database you can / should call the adminconsole with a parameter to use the Provider Locale of choice:
German: "C:\Program Files\Microsoft Configuration Manager Console\AdminUI\bin\adminconsole.msc" sms:ProviderLocale=MS\0x407
English: "C:\Program Files\Microsoft Configuration Manager Console\AdminUI\bin\adminconsole.msc" sms:ProviderLocale=MS\0x409
This should do the trick :-). In my case it always worked.