Apple Support Communities > Servers and Enterprise Software > Mac OS X Server v10.6 Snow Leopard > Discussions
This discussion is archived
4067 Views 4 Replies Latest reply: Aug 16, 2010 3:24 PM by Tim Bloom1
Currently Being ModeratedJun 23, 2010 11:13 AM (in response to Tim Bloom1)Has anyone ever ran across this problem or is it just me?
Currently Being ModeratedJun 26, 2010 10:13 PM (in response to Tim Bloom1)You can change the server's organization by editing the file /etc/systemserialnumbers/xsvr (the first line is the serial number, second is the registrant and organization, separated by a "|". If this doesn't work, try creating a new certificate, and this time enable "Let me override defaults", and it'll let you put in the Organization you want.MacBook Pro, Mac OS X (10.6.2)
Currently Being ModeratedJun 27, 2010 5:41 AM (in response to Tim Bloom1)Or use a different certificate vendor, or call up the current certificate vendor and tell them to look at and resolve this, or (for your own systems and affiliated systems' use) use your own (free) certificate chain.
Somewhat surprisingly, swapping certificate vendors isn't flagged by most web browsers, and that's arguably a risk itself.
If you're not doing remote commercial access and if you have a trusted path to load the root certificate into your clients, then your own certificate is an option.
Currently Being ModeratedAug 16, 2010 3:24 PM (in response to MrHoffman)I was able to do the "override" and put in the organization name manually and get the certificate issued properly via NetworkSolutions. I decided not to change the organization name manually after talking with an Apple engineer on the phone who stated that it's tied in with registration in their system. So I decided it was best to not mess with that if possible.