Adding an a domain alias

Dear All,
Would anyone please point me how can I add a domain alias for my existing domain...
let's suppose my existing domain has the following dn
dn: o=company.com,dc=company,dc=com
my new alias should be in the form
o=com-pany.net,dc=company,dc=com
I am using messaging server 6.3 and DSEE 6.3
Thanks,
Scotty

s@mira123 wrote:
Would anyone please point me how can I add a domain alias for my existing domain...
let's suppose my existing domain has the following dn
dn: o=company.com,dc=company,dc=comIf you are using schema 2 then domain 'aliases' are set with the associatedDomain attribute.
http://docs.sun.com/app/docs/doc/819-4428/bgahk?a=view
So to add an "alias" domain you add the appropriate associatedDomain e.g.
dn: o=company.com,dc=company,dc=com
associatedDomain: com-pany.netRegards,
Shane.

Similar Messages

Adding multiple e-mail alias addresses to an account

Can someone please tell me how to add another e-mail address to my Mail account. I have tried using info from the Mail Help file, both "adding another account" and "adding multiple e-mail alias addresses to an account". Each time when I try to send a test message to or from the added e-mail address, I get the same message: "Cannot send message using the server mail.bellsouth.net. Use the Pop-up menu below to try a different outgoing mail server". The only pop-up is smtp .Mac.
I have tried both methods shown in the HELP file and get the same message. I would really appreciate your help.

Are you trying to add a second email account to Mail, or just add a second "(apparently) from" address to an existing account?
If the former, we need to know some more detail, like:
(1) who is the existing account, .mac or bellsouth?
(2) Which are you trying to add, .mac or bellsouth?
(3) I assume your ISP is Bell South?
(4) What are the names of the smtp servers and what are their respective smtp server port numbers?
(5) Are either of them using SSL on the smtp server?
(6) I don't remember whether Tiger Mail has it or not, but in Leopard Mail, on the menu bar under "Window" there is a selection "Connection Doctor." If applicable to Tiger Mail, what does it say about your connections?
(7) Which account can you send mail through and which one can't you send mail through?
(8) Are your receiving mail okay through either or both accounts? Which one(s)?
Now if you are trying to add a second "(apparently) from" address to an existing account, in Mail Prefs > Accounts > mail account > Email Address, just add a second email address separated by a comma like so:
[email protected], [email protected]
You could have an issue with bellsouth or .mac requiring the domain name in the apparently from email address to match the domain name of the smtp mail server.

Still about domain alias and domain migration

Our company is under a domain name transition. Currently, our domain is lab.D.com, and we are moving to aaa.com.During the transition, we wish both domains could work for us for a long time.
I added a domain alias aaa.com for our domain lab.D.com, the ldif shows:
dn: dc=aaa, dc=com, o=internet
objectclass: alias
objectclass: inetDomainAlias
aliasedObjectName: dc=lab, dc=D, dc=com, o=internet
dc: aaa
after restarting msg server, I can send email to [email protected] which is acutually [email protected]
However, this is only half-way to my goal. I wish our emails at receivers' mailboxes were [email protected], not [email protected], if we send emails though loging in web mail typing [email protected] in the user ID box, or by creating [email protected] accounts in MS Outlook.
===> Is there any way to do it?
===> can [email protected] account be created in MS Outlook?
In another post about domain migration, you suggested:
If you want to stop using the old domain, and make the new domain your "default domain", that's a little harder. It involves several steps:
1. changing all the mail addresses.
2. changing the "default domain" settings everywhere.
===> I wonder, how to do it? is there any command? ldapmodify?
as an alternative approach, if we decide to change our email addresses to [email protected] first,
===> will emails sending to either [email protected] or [email protected] arrive at users who are still in the lab.D.com, if I only change all the mail addresses' domian part to aaa.com since I have added domain alias aaa.com?
and, I do not think sending emails from [email protected] to the internet would be a problem, right???
The iMS we use is iPlanet Messaging Server 5.2 (built Feb 21 2002), Directory Server is 4.16 which are very old versions :(
Thanks.

I make no claim to be a programmer, nor am I expert
with ldap commands.
I know of no easy way to change all, other than
export to ldif, and use a global change with a text
editor, and then re-import.So, db2ldif -> change in text editor -> ldif2db, right?
Another question here is about Direct LDAP.
I enabled Direct LDAP.
aaa.com is the domain alias to lab.oldD.com (our old domain).
I also have changed user alas' email addresss from alas@ lab.oldD.com to [email protected] and added mailAlternateaddress for alas as [email protected], as you instructed in previous posts.
However, whenever I click "send" either to aaa.com or lab.oldD.com, it shows errors, for examples, - "Returning unknown or illegal alias: [email protected]", "Returning unknown or illegal alias: [email protected]"
The log shows:
19:17:27.62: mmc_address_to_tree: Parsing address.
19:17:27.62: Address: "user@[127.0.0.1]" 0x00000000
19:17:27.62: Right default: honey.lab.oldD.com
19:17:27.62: Parsing address with null fixup.
19:17:27.62: mmc_address_to_tree: Returning.
19:17:27.62: Rewriting: Mbox = "user", host = "[127.0.0.1]", domain = "$*", literal = "", tag = ""
19:17:27.62: Rewrite: "$*", position 0, hash table -
19:17:27.62: Found: "$E$F$U%[email protected]"
// honey is our email server
19:17:27.62: Rewrite failed, not forward.
19:17:27.62: Rewrite: "$*", position 1, hash table -
19:17:27.62: Failed.
19:17:27.62: Rewrite: "$*", position 0, rewrite database -
19:17:27.62: Failed
19:17:27.62: Rewriting: Mbox = "user", host = "[127.0.0.1]", domain = "[127.0.0.1]", literal = "", tag = ""
19:17:27.62: Rewrite: "[127.0.0.1]", position 0, hash table -
19:17:27.62: Failed
19:17:27.62: Rewrite: "[127.0.0.1]", position 0, hash table -
19:17:27.62: Failed.
19:17:27.62: Rewrite: "[127.0.0.1]", position 0, rewrite database -
19:17:27.62: Failed
19:17:27.62: Rewriting: Mbox = "user", host = "[127.0.0.1]", domain = "[127.0.0.]", literal = "1", tag = ""
19:17:27.62: Rewrite: "[127.0.0.*]", position 0, hash table -
19:17:27.62: Failed
19:17:27.62: Rewrite: "[127.0.0.]", position 0, hash table -
19:17:27.62: Failed.
19:17:27.62: Rewrite: "[127.0.0.]", position 0, rewrite database -
19:17:27.62: Failed
19:17:27.62: Rewriting: Mbox = "user", host = "[127.0.0.1]", domain = "[127.0.]", literal = "0.1", tag = ""
19:17:27.62: Rewrite: "[127.0.*.*]", position 0, hash table -
19:17:27.62: Failed
19:17:27.62: Rewrite: "[127.0.]", position 0, hash table -
19:17:27.62: Failed.
19:17:27.62: Rewrite: "[127.0.]", position 0, rewrite database -
19:17:27.62: Failed
19:17:27.62: Rewriting: Mbox = "user", host = "[127.0.0.1]", domain = "[127.]", literal = "0.0.1", tag = ""
19:17:27.62: Rewrite: "[127.*.*.*]", position 0, hash table -
19:17:27.62: Failed
19:17:27.62: Rewrite: "[127.]", position 0, hash table -
19:17:27.62: Failed.
19:17:27.62: Rewrite: "[127.]", position 0, rewrite database -
19:17:27.62: Failed
19:17:27.62: Rewriting: Mbox = "user", host = "[127.0.0.1]", domain = "[]", literal = "127.0.0.1", tag = ""
19:17:27.62: Rewrite: "[]", position 0, hash table -
19:17:27.62: Found: "$E$R${INTERNAL_IP,$L}$U%[$L]@tcp_intranet-daemon"
19:17:27.62: Mapping: name = "INTERNAL_IP", input = "127.0.0.1".
19:17:27.62: Mapping 2 applied to 127.0.0.1
19:17:27.62: Entry #2 matched, pattern "127.0.0.1", template "$Y", match #0.
19:17:27.62: New target ""
19:17:27.62: Exiting...
19:17:27.62: Final result ""
19:17:27.62: Mapping result:
19:17:27.62: New mailbox: "user".
19:17:27.62: New host: "[127.0.0.1]".
19:17:27.62: New route: "tcp_intranet-daemon".
19:17:27.62: New channel system: "tcp_intranet-daemon".
19:17:27.62: Looking up host "tcp_intranet-daemon".
19:17:27.62: - found on channel tcp_intranet
19:17:27.62: mmc_winit('tcp_intranet','[email protected]','') called.
19:17:27.62: mmc_determine_url beginning with pattern , xadr , mbox , subaddress
19:17:27.62: Queue area size 18871794, temp area size 18871794
19:17:27.62: 4717948 blocks of effective free queue space available; setting d
isk limit accordingly.
19:17:27.62: mmc_address_to_tree: Parsing address.
19:17:27.62: Address: "[email protected]" 0x00000000
19:17:27.62: Right default: lab.oldD.com
19:17:27.62: Parsing address with local fixup.
19:17:27.62: mmc_address_to_tree: Returning.
19:17:27.62: Rewriting: Mbox = "alas", host = "newD.com", domain = "$*", literal
= "", tag = ""
19:17:27.62: Rewrite: "$*", position 0, hash table -
19:17:27.62: Found: "$E$F$U%[email protected]"
19:17:27.62: Rewrite failed, not forward.
19:17:27.62: Rewrite: "$*", position 1, hash table -
19:17:27.62: Failed.
19:17:27.62: Rewrite: "$*", position 0, rewrite database -
19:17:27.62: Failed
19:17:27.62: Rewriting: Mbox = "alas", host = "newD", domain = "newD.com", litera
l = "", tag = ""
19:17:27.62: Rewrite: "newD.com", position 0, hash table -
19:17:27.62: Failed.
19:17:27.62: Rewrite: "newD.com", position 0, rewrite database -
19:17:27.62: Failed
19:17:27.62: Rewriting: Mbox = "alas", host = "newD", domain = ".com", literal =
"", tag = ""
19:17:27.62: Rewrite: "*.com", position 0, hash table -
19:17:27.62: Failed
19:17:27.62: Rewrite: ".com", position 0, hash table -
19:17:27.62: Found: "$U%$H$D@TCP-DAEMON"
19:17:27.62: New mailbox: "alas".
19:17:27.62: New host: "newD.com".
19:17:27.62: New route: "TCP-DAEMON".
19:17:27.62: New channel system: "TCP-DAEMON".
19:17:27.62: Looking up host "TCP-DAEMON".
19:17:27.62: - found on channel tcp_local
19:17:27.62: mmc_address_to_tree: Parsing address.
19:17:27.62: Address: "[email protected]" 0x00000000
19:17:27.62: Right default: lab.oldD.com
19:17:27.62: Parsing address with null fixup.
19:17:27.62: mmc_address_to_tree: Returning.
19:17:27.62: Rewriting: Mbox = "alas", host = "newD.com", domain = "$*", literal
= "", tag = ""
19:17:27.62: Rewrite: "$*", position 0, hash table -
19:17:27.62: Found: "$E$F$U%[email protected]"
19:17:27.62: Rewrite failed, not forward.
19:17:27.62: Rewrite: "$*", position 1, hash table -
19:17:27.62: Failed.
19:17:27.62: Rewrite: "$*", position 0, rewrite database -
19:17:27.62: Failed
19:17:27.62: Rewriting: Mbox = "alas", host = "newD", domain = "newD.com", litera
l = "", tag = ""
19:17:27.62: Rewrite: "newD.com", position 0, hash table -
19:17:27.62: Failed.
19:17:27.62: Rewrite: "newD.com", position 0, rewrite database -
19:17:27.62: Failed
19:17:27.62: Rewriting: Mbox = "alas", host = "newD", domain = ".com", literal =
"", tag = ""
19:17:27.62: Rewrite: "*.com", position 0, hash table -
19:17:27.62: Failed
19:17:27.62: Rewrite: ".com", position 0, hash table -
19:17:27.62: Found: "$U%$H$D@TCP-DAEMON"
19:17:27.62: New mailbox: "alas".
19:17:27.62: New host: "newD.com".
19:17:27.62: New route: "TCP-DAEMON".
19:17:27.62: New channel system: "TCP-DAEMON".
19:17:27.62: Looking up host "TCP-DAEMON".
19:17:27.62: - found on channel tcp_local
19:17:27.62: Mapped return address: [email protected]
19:17:27.62: mmc_rrply: Return detailed status information.
19:17:27.62: mmc_rrply: Returning return address and channel OK
19:17:27.62: mmc_wadr(0x001abd40,'','[email protected]') called.
19:17:27.62: Copy estimate before address addition is 1
19:17:27.62: Parsing address [email protected]
19:17:27.62: mmc_address_to_tree: Parsing address.
19:17:27.62: Address: "[email protected]" 0x00000000
19:17:27.62: Right default: lab.oldD.com
19:17:27.62: Parsing address with local fixup.
19:17:27.62: mmc_address_to_tree: Returning.
19:17:27.62: Rewriting: Mbox = "alas", host = "lab.oldD.com", domain = "$*", l
iteral = "", tag = ""
19:17:27.62: Rewrite: "$*", position 0, hash table -
19:17:27.62: Found: "$E$F$U%[email protected]"
19:17:27.62: Match, pattern = "lab.oldD.com", current = "(*domaincheck*)"
19:17:27.62: old state = not checked.
19:17:27.62: Performing domainMap check on lab.oldD.com.
19:17:27.62: Added domainMap result 1 to cache for lab.oldD.com.
19:17:27.62: new state = succeeded.
19:17:27.62: New mailbox: "alas".
19:17:27.62: New host: "lab.oldD.com".
19:17:27.62: New route: "honey.lab.oldD.com".
19:17:27.62: New channel system: "honey.lab.oldD.com".
19:17:27.62: Looking up host "honey.lab.oldD.com".
19:17:27.62: - found on channel l
19:17:27.62: Routelocal flag set; scanning for % and !
19:17:27.62: Address [email protected] requires local processing.
19:17:27.62: Variant #1 = [email protected]
19:17:27.62: Variant #2 = *@lab.oldD.com
19:17:27.62: Checking for [email protected] in the system alias file
19:17:27.62: - not found
19:17:27.62: Checking for *@lab.oldD.com in the system alias file
19:17:27.62: - not found
19:17:27.62: - adding address [email protected] to headers.
19:17:27.62: Copy estimate after address addition is 1
19:17:27.63: mmc_rrply: Return detailed status information.
19:17:27.63: mmc_rrply: Returning unknown or illegal alias: [email protected]
I wonder why?
Thanks.

Domain alias problem

Hi Jay and all,
we are running Sun Java messaging 2004Q4 on solaris 9.
We want to create a domain alias so that our server can receive mails on different domain also.
Let's say we have already x.com and want y.com to be domain alias for it. So i ran this below script and it was successful
++++++
echo dn: o=x.com,dc=x,dc=com >>/sbin/ldap99.txt
echo changetype: modify >>/sbin/ldap99.txt
echo add: associatedDomain >>/sbin/ldap99.txt
echo associatedDomain: y.com >>/sbin/ldap99.txt
cd /var/opt/mps/serverroot/shared/bin
./ldapmodify -D uid=admin,ou=people,o=x.com,dc=x,dc=com -w <admin-pass> -R -f /sbin/ldap99.txt
++++++++++++++
Now i suppose y.com has become an alias to x.com so that i can receive mails destined to [email protected] also and get them forwarded to the [email protected] mailbox (No need for user level aliasing again)
But when i say "telnet <mail-server> 25" and rcpt to:[email protected], it says "550 5.1.1 unknown or illegal alias: [email protected]".
it means that the vanity domain created successfully but not able to identify users already created on x.com (it did not throw the error - 550 5.7.1 Relaying not allowed: [email protected])
Please advise me.
TIA
Prvn

Hi,
Now i suppose y.com has become an alias to x.com so
that i can receive mails destined to [email protected] also
and get them forwarded to the [email protected] mailbox (No
need for user level aliasing again)You still need to add the user-level address attribute e.g.
mailalternateaddress: [email protected]
Just adding the associatedDomain attribute doesn't automatically result in emails sent to [email protected] being delivered to the mailbox of [email protected]
But when i say "telnet <mail-server> 25" and rcpt
to:[email protected], it says "550 5.1.1 unknown or illegal
alias: [email protected]".
Try adding the mailalternateaddress: [email protected] to the [email protected] account.
Regards,
Shane.

Setting up a Mail domain Alias

Hi
We are trying to set up a mail domain alias so that a user can receive mails on either [email protected] or [email protected], the default mail domain on which OCS has been installed is domainA.com
I've tried the rewrite rules for inbound SMTP as:
Pattern To Match
$[email protected]
Action
Apply Rewrite
Rewrite To Apply
$[email protected]
But it does not seem to work (I'm just not receiving any test mails and don't know where we can check for logs for any discarded mails)
Is there any simple way to set up this 'maildomain alias'?
Many thanks for your assistance
Rgds
Vicky

Marc,
In this situation, I think you only need to add the additional addresses, into the Email Address entry box in Mail Preferences/Accounts/Account Information. You put a comma after the existing address, and add another. Put a comma after the new, one, and you can add still another.
http://docs.info.apple.com/article.html?artnum=302215
and
http://docs.info.apple.com/article.html?path=Mail/2.0/en/ml1019.html
You will need to be sure to select the correct one, in each reply or new message. The latter link is also found in Mail Help.
Does this fulfill your need?
Ernie

Domain Alias approch - Best Practice Request

Hello,
I am managing a company that has many domains. We have been using standard sendmail for mail server.
I have set it up through relay-domains etc... such that a user can get mail at any of the listed domains (there are 76 of them!). So, if I have jdoe mail will route to that user if you send mail to [email protected], [email protected] etc... all 76 of them.
My question is how to best replicate this functionallity with minimal (one time?) administration in msgsrvr... imta.cnf? some other means?
Thanks for reading...
Mike

Mike, this question looks very much like the one that's been getting discussion in the ims-info forum. Please understand, I read that forum, daily. . .
The advise you get there should be considered totally authoratative.
Domain Alias is indeed the correct way to have our Messaging Server handle this task for you.

Domain alias in iMS 5.2

Hi,
Objective: The Users of Domain abc.com want that mails can be sent to them at xyz.com domain too.
Methods: flat alias file (not recommended)
vanity Domains ( fit for small no of users only)
Domain Alias ( recommended)
Discussion:
I created a Domain alias for abc.com to be xyz.com
ldif used
=======
dn: dc=xyz,dc=com,o=internet
objectclass: alias
objectclass: inetDomainAlias
aliasedObjectName: dc=abc,dc=com,o=internet
dc: xyz.com
ldapmodify -a -D "cn=Directory manager" -w mypassword -f aboveldiffile
My option.dat has entries for aliasurl and alias magic
Now I try to login using user@xyz : success
I try to send mail to user@xyz instead of [email protected]: failure
What happens ..in directpry access logs:
dc root is checked for xyz domain ...on finding ...the search base is adjusted to abc.com....
But now the e-mail address searched for is [email protected]..in domain abc ...which is not set ...
SO I DEFINE ALTERNATEMAILADDRESS ATTRIBUTE FOR DOMAIN USERS ABC.COM
so that search matches...
Now things work fine ....
I also check some postings here on the sunbject ....
where JAY suggests to use DOMAIL_LEVEL = 2 in option.dat file..
I delete mailalternateaddresses ...for users add DOMAIN_UPLEVEL=2...
now sendinf mail addressed at [email protected] suceeds....
Looing at ldap access logs I find ...that the search is directly started at abc.com ???
and the mails searched for are [email protected] aswell as [email protected] ...
So my concern is WHAT DOES DOMAIN_LEVEL actually DO????
Thanks

For a very good description of how direct ldap works, please see here:
http://docs.sun.com/source/816-6009-10/dirldap.htm#27650

Create domain alias

I created domain alias using the following LDIF sentences:
A:
dn: dc=b, dc=a, dc=com, dc=cn, o=internet
changetype: add
objectclass: alias
objectclass: inetDomainAlias
aliasedObjectName: dc=x, dc=y, dc=com, o=internet
dc:b
Later, I also tried B::
dn: dc=b.a.com.cn, o=internet
changetype: add
objectclass: alias
objectclass: inetDomainAlias
aliasedObjectName: dc=x, dc=y, dc=com, o=internet
dc:b.a.com.cn
it seemed both works.
I wonder which way is right?
or, when should I use which?
thanks.

Let me clarify over the previous clarification:
my goal:
A. When users send emails to internal addresses
([email protected] and [email protected]), the senders' addresses
should be looks like [email protected] or
[email protected] at the recipients' mailboxes, in
another word, the "from" section of the email.
And,
B. When users send emails to external addresses
including [email protected] and other
address, e.g. [email protected], "from" sections of
senders' emails should be like [email protected], or
[email protected]
That is, users from the Internet will only see the [email protected]/[email protected] address.
>
So,
What I am thinking is:
1. apply rewrite rule at tcp_local to rewite the
"from" section of emails sent to the Internet
2. create domain alias b.a.com.cn and c.b.a.com.cn
for x.com and y.x.com respectly.
So emails sent to [email protected]/[email protected] will be delivered to [email protected]/[email protected]
>
I do not think I need to add mailalternateaddress to
each user's defination in ldif. Right?
Would this work?
Thanks.Thank you.

Error: Key already added to dictionary " domain \ username "

Hello Community
    In Sharepoint 2013 Server I created a managed account.
    But when I try to create the Search Service application
with that managed account as the configurable an error message
appears stating some to the effect that:
     Key already added to dictionary "<domain>\<username>" : ... "<domain>\<username>"
    Since I couldn't use that same "<domain>\<username>", I created
another new managed account and used that new managed account to create
the Search Service and it worked.
    The question is why do I get that error stating:
        Key already added to dictionary "<domain>\<username>" : ... "<domain>\<username>" ?
    Thank you
    Shabeaut

Is it specific to some particular managed account or for all the managed accounts ?
Does that managed account exists twice ?
Have a look at the following links if it gives you any pointers.
https://tayzarminn.wordpress.com/2013/03/21/getting-error-like-item-has-already-been-added-key-in-dictionary-while-removingediting-managed-account-in-sharepoint-2010/
http://sharepointgoose.blogspot.in/2012/08/getting-error-item-has-already-been.html
Geetanjali Arora | My blogs |

Rewrite Rules with Domain Alias

Version:
iPlanet Messaging Server 5.2 HotFix 2.03 (built Nov 22 2004)
libimta.so 5.2 HotFix 2.03 (built 13:20:08, Nov 22 2004)
I am hosting 1 domain with an domain alias for the same hosted domain.
I would like all mail coming in as domain A to be rewritten as domain B. Same for all outgoing mail outgoing as domain A to rewritten as domain B
What should my rewrite rules look like?
domain.a $U%domain.b

That makes senses. I am using mailequivalentaddress with a domain alias. I also have the following rule in my imta.cnf:
domain.A $R$U%domain.B
domain.A $U%domain.B
There rewrites all of the mailheaders but I noticed the the envelope headers are not rewritten. Is it a good idea to rewrite the envelope headers although the domain beinging rewritten to is an alias? The mail headers on the to: and from: address are rewritten as domain.B but envelope headers show [email protected] for delivery.

Workaround to adding two e-mail alias accounts with same username.

I have two e-mail addresses (aliases) (for example [email protected] and [email protected]) running under one (same) username "jimmy" and the same password on the same mail server (basically one e-mail account with two e-mail address aliases). I wanted to have both added to my iPad running iOS 5. I added the first without a problem, but when I tried to add the second one, the iPad complained that an account with the username "jimmy" already exists and gave me a prompt window with two options, "Cancel" and "Edit". Cancel was supposed to cancel the whole e-mail account creating procedure and take me back to Settings/Mail, and "Edit" was supposed to take me back to editing this e-mail account so I could change it (select another username). It turned out that both "Cancel" and "Edit" threw me out of the editing procedure and put me back into Settings/Mail. Seems like a bug.
I managed to use a workaround to add my second e-mail address account (alias) to the iPad 2 with the same account username. I started creating the second account and filled in all the information but I intentionally mystyped the username as "jimmo". Now when I tapped "Done" the iPad wanted to verify the account (as normal) but soon warned me that either the username or password were incorrect and that the account may not work correctly, but it did allow me to add it. I then went in and edited this second account and changed it's incoming mail server username to "jimmy".
Now I have both e-mail addresses (aliases) using one account correctly set-up. Just thought I'd write this in case anyone would encounter the same problem/bug.

EDIT: When using Mail application to check e-mails I am getting sporadic "Cannot Get Mail: The user name or password for "<name_of_account> is incorrect." The password is correct and it works when I retry. If I disable one of the accounts in the Settings/Mail (set to Inactive) then the other one (using the same password on the same server) works without hiccups. They definitely have to work on this bug and fix it.

Recently Added Office 365 Domain to Azure

We just signed up with Azure and I'm in the process of building it out. We also have an existing Office 365 subscription which we use primarily for email (Exchange 2013 in Office 365). The trouble is that I'm fairly new to Office 365 and a complete noob
when it comes to Azure, so everything I'm doing to get these two worlds to talk is self taught (we do not have support).
In an effort to get a head start, in Azure, I have built two servers to be designated as domain controllers and two servers to be designated as application servers; a total of four virtual servers now exist in Azure. I installed the respective roles
on each of the servers.
This morning I finally managed to understand how to link our existing Office 365 domain to Azure; the Office 365 directory now exists in Azure. Subsequently, I attempted to promote the two virtual servers to domain controllers in the recently added
directory to no avail. When I begin the promotion, I select the option to
Add a domain controller to an existing domain, enter the domain name (Office 365) and the domain admin creds, and then I'm met with the following error:
An Active Directory domain controller for the domain "name of domain" could not be contacted
Basically, when I attempt to add this to server to that domain I'm met with an error that no domain controller exists or if I attempt to promote the server to a domain controller I'm met with the error above. How do I get around it? How can I
successfully add either of the newly provisioned virtual servers to the domain?
Any help you can offer would be great!

Marcin is correct.
For better understanding, imagine Windows Azure Active Directory as an Organizational Unit (OU), in which you can manage user accounts and groups, but no any computer accounts. WA AD is for handling authentications, and because Office 365 (which is a SaaS)
authenticates with WA AD, and an Azure subscription is also using WA AD object for authentications, you can import WA AD of an Office 365 subscription into Azure.
On the other hand if you build your own network and infrastructure in Azure, and needs a Domain Controller, you need to install a VM with Active Directory Domain Services role.
Regards,
Tibor Veszprémi
Systemfarmer

Adding WebLogic Server Domain fails with UnsupportedClassVersionError

Hi all,
I am trying to add a WebLogic Server 10.3 domain to the Grid Control, but receive the following error:
java.lang.UnsupportedClassVersionError: weblogic/jndi/Environment (Unsupported major.minor version 49.0)
The discovery wizards asks for 'Administration Server Home Directory'
The help document states:
If you are adding BEA WebLogic Manager Server Release 9.x or higher, then specify the absolute path to the directory
where wljmxclient.jar and wlclient.jar files are located. For example, <WL-HOME>/server/lib.
The JDK version of BEA WebLogic is 1.6.x
The JDK version of the Grid Agent is 1.4.2
Clearly their is a mismatch here!
Is there any solution to this?
Thanks,
Knut
Edited by: user585799 on Feb 17, 2009 2:13 AM

This is not a supported configuration .10.2.0.4 GC is not certified with WLS 10.3
Edited by: mnazim on Feb 17, 2009 2:56 AM

Adding a second Domain Controller

...ok, so what you're saying is, If I don't spread out the FSMO roles, when the primary DC fails, I will likely run into problems until I seize the FSMO roles and delegate them to the secondary DC? By spreading out the FSMO roles, I am creating less work for myself in the event of a failure?
...Having said that, it isn't critical that I spread out the FSMO roles, but, would benefit me in the event of failure from a time stand point?

I'm sitting at about 95% completion... but before I click finish, I had a few questions...
I have a physical domain controller and Site-A, I want to add a secondary Domain Controller to Site-A and run it as a Virtual Machine... just in case the first DC dies, my users can still authenticate while I restore it from backup...
I'm essentially adding a new DC to the existing domain, Global Catalog, DNS... not read only...
I don't understand FSMO... do I need to do anything? or can I literally just add the second DC to the existing domain, enter the IP of the new DC in the secondary DNS on all my workstations (or DHCP leases settings) and call it a day?
Thanks for the input.. .just trying to make sure I'm not going to hose my primary DC or fek something up and create more work for myself than necessary...
This topic first appeared in the Spiceworks Community

Adding a second domain controller to domain

Neally I can do that no problem but why it is asking me again when it was already done when I added my first 2008 R2 Domain Controller . I will try running it again and post the results.
Thanks

Hi ,
I am trying to add a second Windows 2008 R2 domain controller to a existing domain.
but its asking me to run adprep/forestprep but I already have domain controller that is a Windows Server 2008 R2 and it is also a Schema Master Role holder .
Any help is this regards will be much appreciated.
Thanks
Sunny Boparai
This topic first appeared in the Spiceworks Community

Adding an a domain alias

Similar Messages

Maybe you are looking for