WSEE Installer on Win2025 Std
We are in process of replacing the old 2019 server (with WSEE installed & working great!) with 2025 Std.
- I installed the server 2025 os & downloaded/installed your WSEE installer
- During the “Configure Windows Server Essentials” step, I get this message:
- “The internal domain name has an invalid format. Your input contains invalid characters or is too long.“
- No matter what I type in the “Internal Domain Name” field, it stops with this error?
On the Company Information step of the wizard: Here’s what the values should be for the new server:- Company Name: Brown and Roberts
- Internal Domain Name: ad.brownandroberts.com
- Server name: Server6
What am I doing wrong? Thanks for your help & thanks for a great piece of software.
- jlig asked 3 months ago
- You must log in to post comments.
I’ve never come across such an issue in Windows Server Essentials before, but then again, I’ve never attempted to use an internal domain name outside of anything but the default/suggested MyCompanyName.local I’m afraid.
I do believe that .com is an accepted/allowed TLD for the internal domain name, and so I imagine that your problem is with the “ad.” portion. I assume (but do not know for sure) that format is not allowed in Essentials and that is what’s causing your issue. Thus, you’ll most likely need to drop the “ad.” and just use “brownandreoberts.com” instead (again though, this is not my area of specialty, and so I cannot say for sure).
- Mike answered 3 months ago
- last edited 3 months ago
- You must log in to post comments.
Mike, thanks for the reply.
- strangely, it won’t even accept default values
- or brownandroberts.com
- or brownandroberts.local
The recommendation from Microsoft is to use “sub-domains” & ad. is a best recommendation. Thanks again.
- jlig answered 3 months ago
- You must log in to post comments.
Out of curiosity… Is this a brand new/clean (i.e. straight out-of-the-box) install of 2025 (or was it migrated over from 2019)? If not, then have you tried testing a new/clean install to see if it accepts the internal domain name that way (just for kicks)? At the very least, it’ll tell you if there’s an issue with your domain name or with the server install itself (as I don’t see why brownandroberts.com nor .local shouldn’t be working).
- Mike answered 3 months ago
- Mike, thanks again for the reply. – unfortunately, yes I have tried it on a clean install of 2025 Std Here is what’s even stranger: – I originally did a trial install of 2025 Std on a spare laptop – Then I ran your WSEE Installer Version: 10.0.14393.7969 (Rev 1) – Then I ran the configuration & it worked using the ad. subdomain – Once the new Dell server arrived I installed the same WSEE Installer Version & get that error? – Thinking that the Dell 2025 Std install may be the issue, I wiped it & reinstalled a clean 2025 Std. – Got the same error again? The only thing that changed was the physical Dell server. – I may try & “image” the laptop install “over to” the new Dell server. PS: Do I need to purchase another WSEE license key from you for the new server? It will be months before we decommission the old 2019 server.
- That’s definitely a strange one that leaves me baffled I’m afraid. As for the WSEE license… The WSEE Installer is set up to only allow its license to be used on one server install at a time (i.e. it’s one server install per purchased product). Thus, if you want/need to use WSEE on more than one server (even for a brief period of time), then each server would indeed require its very own license I’m afraid.
- You must log in to post comments.
