Thanks, guys. My boss asked me to do some research and check out what we've heard from some vendors. I like to get input from several sources to get an informed analysis. Not to mention that we have several non-technical people involved that always ask for more details. I greatly appreciate...
Dave, I did not mean to offend you. I simply asked a question in order to get a better response with which to give to my boss and justify my response. I was under the assumption that this was a site for such things. If not, I greatly apologize.
Will any problems using a 2000 DC have any devastating affects? I only ask, because we are in the process of moving to Server 2003 -> Server 2008 (Gotta take baby steps) in the near future, but would like to get our Exchange server going and migrate the data 1st.
Also, are any ill affects...
Hey gang. We are currently migrating to Exchange 2007 as the title suggests. We have heard conflicting stories as to whether it would be too much of a pain to go straight from 2000 to 2007. It was suggested to go to 2003 1st, then go to 2007. Any thoughts?
Well, we are going to a SAN/Blade environment regardless of which way we go. AS noted by xmsre, Microsoft isn't exactly big on the idea. Actually, only IBM has come out and said it will work and I have spoken to someone who has it running in a much bigger environment (we have about 150-200...
58 sniper,
Even with the fiber connection? And is it hardware dependent? We're looking at IBM, Dell and HP blade environments. Ohh, I forgot to add the SAN that we want to use as well.
We are currently looking into going into a blade environment. One of the issues that we have bumped into concerns running Exchange 2007 in a blade environment. We have talked with several vendors and the answers vary. Some say it will have production issues and must be run on a server outside...
Sorry for just checking back in.
It is an internal IP address due to the 192.168 part of it, unless I'm wrong. I did a tracert on it and it went to an outside source. Turns out that it was an old modem that was outside the network that was used for something else. The cabling in the building...
I've tested inside from a local machine. Pings come back timed out. I can check the router, but there isn't even a DNS record of it existing. It's an internal IP address.
Everything that utilizes the network fails. Loses IP address, can't connect to network resources, the whole nine.
I have a network that consists of serveral off site locations. One location is using an IP address that is outside the assigned range for that location as a gateway and as a DNS server. The problem is that that IP address doesn't exist. There is no server, workstation, swtich, router, etc...
Hawk, I'll give it a shot. I did try importing it to Outlook 2003 and then exported it into a pst file. But I don't think XP can use .pst files from 2003, as is evident when it didn't work.
Hawkdaddy, far as I can tell, Express lacks some functionality, but I can't tell you anymore than that.
It should import right in, but it's asking for some translator add-in.
I am having a problem with Outlook XP. A new emmployee is trying to import a contact list in Excel into Outlook XP and the application is trying to load a translator. I can't get the translator to load, as I can't find it. Any ideas?
We are looking at possibly using a unified communications platform and have been asked to do some research. Is there anywhere I can look and are there any major differences in the hardware vs software UCP(s)?
miguelmiggs,
Thanks, that seemed to work. Using ntdsutil, I thought you had to set the connection to the failed server in order to use it. You only need to connect to any server in the domain to remove it and it should replicate to the others.
Thanks everyone!!!
58 sniper,
Saw that one. Problem is that the server is not connected to the domain and without a connection, connect to server will not work. I can't rejoin it as is now because I get a message saying that it already exists.
Seaspray,
I was able to demote it using dcpromo /forceremove. It seems to have worked, but I'm a bit concerned about lingering data. I renamed it and rejoined it to the domain and the logs haven't shown any problems. Is there a way to remove the old name from the domain without having to...
OK, I got the machine removed using the dc promo /forceremoval command. Now I need to remove it from the network as far as the other servers are concerned. Meaning that the others are still trying to communicate with the server no longer in the domain. It's not a huge deal, but I'd like to...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.