Sunday not as productive as Saturday.
I started off with all the clients connected to the server using http://connect, the server ready to setup the certificates...
Then GoDaddy tells me I can't use .local for my internal domain; as I had selected a 3 year certificate. So my options were, not add certificate for server, reduce to 2 years and deal with later, or sort it out properly now. I went with the later.
So I couldn't just change the domain name in SBS 2011, I had to reinstall the whole thing. Then when I get the stage in the wizard that asks for domain name, it forces me to use .local! So I reinstall the server again and instead I use the Answer File Tool to enter my server name, internal domain as DomainA and full DNS as a subdomain ad.DomainA.com. Then off it went installing SBS 2011. When it loaded to desktop it spent the rest of the day downloading millions of updates, service packs etc. Just finished this morning. went through the wizards, added the users, but not added the certificate yet.
I went to each of the clients to reconnect to the new domain and none of them allowed me to select the user's profile as it had before and restoring the machines to an earlier date would leave their profiles corrupted, so I've asked everyone to empty their profiles of any data and I'll then go round and setup new workgroup profiles for each and then clean up all the old redundant profiles, then http://connect should work again.
Dyn is now temporarily redirecting DomainA emails to 1and1 webmail using 1and1's MX servers.
I have my architect hat on today, so not much progress until this evening when I can put my IT admin hat on.
I started off with all the clients connected to the server using http://connect, the server ready to setup the certificates...
Then GoDaddy tells me I can't use .local for my internal domain; as I had selected a 3 year certificate. So my options were, not add certificate for server, reduce to 2 years and deal with later, or sort it out properly now. I went with the later.
So I couldn't just change the domain name in SBS 2011, I had to reinstall the whole thing. Then when I get the stage in the wizard that asks for domain name, it forces me to use .local! So I reinstall the server again and instead I use the Answer File Tool to enter my server name, internal domain as DomainA and full DNS as a subdomain ad.DomainA.com. Then off it went installing SBS 2011. When it loaded to desktop it spent the rest of the day downloading millions of updates, service packs etc. Just finished this morning. went through the wizards, added the users, but not added the certificate yet.
I went to each of the clients to reconnect to the new domain and none of them allowed me to select the user's profile as it had before and restoring the machines to an earlier date would leave their profiles corrupted, so I've asked everyone to empty their profiles of any data and I'll then go round and setup new workgroup profiles for each and then clean up all the old redundant profiles, then http://connect should work again.
Dyn is now temporarily redirecting DomainA emails to 1and1 webmail using 1and1's MX servers.
I have my architect hat on today, so not much progress until this evening when I can put my IT admin hat on.