I have a mm working with no domain info, Avaya states it's impossible but yet it's up and running. I wasn't the one that installed it and there are NO planning forms for this machine. My question is: Does anyone know if there is a way to extract the domain info from the MAS to repopulate the MSS domain field and to create a new set of planning forms for future use? My fear is that one day this machine will cease to operate and without that info I don't stand a chance to recover.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
MM 2.0 operating with no damain info
- Thread starter ken07734
- Start date
You can try to run rhe dct tool to pull some info from the mas.
Are you saying that the vmsc does not show a VMD or the MAS is not in a domain?
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
Are you saying that the vmsc does not show a VMD or the MAS is not in a domain?
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
- Thread starter
- #3
Strange but like I said use the dct tool and run analyze system to pull any info from the mas
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
- Thread starter
- #5
Well here's the confusing part. Avaya tier 2 instructed me not to do that stating that it may create a new domain and cause the current information on the MSS to be unusable. I'm pretty good with MM and the Microsoft OS and this gives me shivers. MY current thought is to make a backup of the MAS and then a full attended backup of the MSS with the messaging stopped. reload the MAS/MSS from scratch using a sit down with company IT manager of customer planning forms and then update to SP 6. Considering there are NO caller applications and they only use it for subscribers at this point it shouldn't be too much of a pain.
There is a way to get into the MSS and find out the default domain name from the TSC prompt. They will not tell me how to do this but I know it can be done. You might be able to get the default domain name and then add the VMD with the same name in the VMSC. If you do a backup on the MSS you would not be able to use the restore as the mailbox GUID would be from the domain it was using and not the new one. We had a 2nd domain popup in a system with 3 MAS'S and all new MB's were in the new on as it was then the primary in the MSS. We removed the domain from the VMSC after deleting all of the new mailboxes and then the alarm stopped in the MSS and all worked well after that.
And do you know who installed this thing with out any plan forms?
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
And do you know who installed this thing with out any plan forms?
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
As a follow-up you can tell what domain the user is in by looking at the FEDB query and then looking at the string after the mailbox number and ext number. in the case below you will see the first one starts with a 0C0 and all of the others are B60 The 0C0 is a different domain in the VMD. I have removed the names from this list so it will look different when you run it.
umObjectGUID=27a83a6c7e1511db9c6f000423c1b467,ou=People,dc=Avaya",7258,7258,0C01679D-E882-406E-9EEF-96279BD8C5FD,7258,**Password**,0,1,0,0,1,3,1
umObjectGUID=f740ebbd131a4bda91eefaa60eea7316,ou=People,dc=Avaya",6466,6466,B6027C7A-63F1-4B5B-83FD-0A8B7E0F1CDD,6466,**Password**,2048,1,0,0,1,3,1
umObjectGUID=2aba355efad1483fb0678a84061b68b0,ou=People,dc=Avaya",7481,7481,B6027C7A-63F1-4B5B-83FD-0A8B7E0F1CDD,7481,**Password**,2048,1,0,0,1,3,1
umObjectGUID=8b7cfbd3e619404288c62b94e4db6008,ou=People,dc=Avaya",7551,7551,B6027C7A-63F1-4B5B-83FD-0A8B7E0F1CDD,7551,**Password**,2048,1,0,0,1,3,1
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
umObjectGUID=27a83a6c7e1511db9c6f000423c1b467,ou=People,dc=Avaya",7258,7258,0C01679D-E882-406E-9EEF-96279BD8C5FD,7258,**Password**,0,1,0,0,1,3,1
umObjectGUID=f740ebbd131a4bda91eefaa60eea7316,ou=People,dc=Avaya",6466,6466,B6027C7A-63F1-4B5B-83FD-0A8B7E0F1CDD,6466,**Password**,2048,1,0,0,1,3,1
umObjectGUID=2aba355efad1483fb0678a84061b68b0,ou=People,dc=Avaya",7481,7481,B6027C7A-63F1-4B5B-83FD-0A8B7E0F1CDD,7481,**Password**,2048,1,0,0,1,3,1
umObjectGUID=8b7cfbd3e619404288c62b94e4db6008,ou=People,dc=Avaya",7551,7551,B6027C7A-63F1-4B5B-83FD-0A8B7E0F1CDD,7551,**Password**,2048,1,0,0,1,3,1
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
- Thread starter
- #8
Which domain name are you talking about? There is the voicemail domain (VMD) which is the voice messaging container for a group of MAS units . There is the private Windows domain which the first MAS creates when it becomes the domain controller, and then there is the corporate domain.
The corporate domain name is easy to change and is done in the basic network addressing section. The private Windows domain is harder to change, but it can be done with an MAS rebuild. The voicemail domain name can't really be changed unless you want to start from scratch.
Chuck
RCT Technologies
The corporate domain name is easy to change and is done in the basic network addressing section. The private Windows domain is harder to change, but it can be done with an MAS rebuild. The voicemail domain name can't really be changed unless you want to start from scratch.
Chuck
RCT Technologies
- Status
Similar threads
- Locked
- Question