Re: removing exchange 2003 objects once exchange 2007 is in place

Was EXCHANGE\0ADEL your Ex 2003 server? How did you decomission this
server? Did you uninstall it gracefully?

Also for the first error did you move your public folder hiearchy?

On your Exchange 2003 or Exchange 2000 server, perform the following
steps to move the public folder hierarchy from the Exchange 2003 or
Exchange 2000 administrative group to the Exchange 2007 administrative
group:

In Exchange System Manager, expand Administrative Groups, right-click
Exchange Administrative Group (FYDIBOHF23SPDLT), select New, and then
select Public Folders Container.

Expand the Exchange 2003 or Exchange 2000 administrative group that
contains the public folder tree, expand Folders, and then drag Public
Folders to Folders under the Exchange 2007 administrative group.



James Chong (MVP)
MCITP | EMA; MCSE | M+, S+,
Security+, Project+, ITIL
msexchangetips.blogspot.com





On Mar 19, 1:30 pm, "William Holmes" <wthol...@xxxxxxxxxxx> wrote:
Hello,

The specific errors from the analyzer are:

The site-wide public folder database for administrative group 'First
Administrative Group' has been deleted. Current public folder store:
CN=Public Folder Store
(EXCHANGE)\0ADEL:558f5d57-e1f8-4a0e-8c56-8391a87520f9,CN=Deleted
Objects,CN=Configuration,DC=mydomain,Dc=com

This makes sense since I uninstalled the Last Exchange 2003 sever but it
seems to me this should have been migrated to the exchange 2007 server.

Server EXCHANGE\0ADEL:2197e01c-e149-40c8-aaff-295ab1d0b6f5 is a routing
group master but a connection to port 25 cannot be established from the
workstation where this tool is running.
.
Server EXCHANGE\0ADEL:2197e01c-e149-40c8-aaff-295ab1d0b6f5 is a routing
group master but a connection to port 691 cannot be established from the
workstation where this tool is running.

The routing groups were all replaced with exchange 2007 routing.

All of the exchange 2003 servers have been removed but some of the objects
seem to be left behind in Active Directory.

Thanks

Bill"Jamestechman" <jamestech...@xxxxxxxxx> wrote in message

news:13cf6ddf-678c-4cd6-a22b-c6d2ca939db3@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
According to this article; I would not delete. Also what is Exchange
Best Practice Analyzer saying?

How to Remove the Last Legacy Exchange Server from an Organization

"You should not delete any Exchange Server 2003 legacy administrative
groups that contain mailboxes at any point of time. The
legacyExchangeDN attribute for each user still references the old
administrative groups. As long as clients are using versions of
Outlook before Outlook 2007, the legacyExchangeDN attributes are used
to find the free/busy data. If the administrative group no longer
exists, we can no longer guarantee that the free/busy data folder will
exist for users who have the matching legacyExchangeDN attribute.
These users might have difficulties finding or publishing free/busy
information. Additionally, legacyExchangeDN attributes are used when
Exchange Server 2007 uses the Outlook client to delegate access to
folders."

James Chong (MVP)
MCITP | EMA; MCSE | M+, S+,
Security+, Project+, ITIL
msexchangetips.blogspot.com

On Mar 18, 11:25 pm, "William Holmes" <wthol...@xxxxxxxxxxx> wrote:



I removed the server from AD. What about the First Administrative Group?
Once exchange 2007 is installed and is running does this need to stay in
AD?
I am just curious.

Bill

"Ed Crowley [MVP]" <cursp...@xxxxxxxxxxxxxx> wrote in
messagenews:uItgq6WiIHA.4868@xxxxxxxxxxxxxxxxxxxxxxx

You should be able to remove the server using Exchange 2003 System
Manager. If that doesn't work, you can follow this:
http://support.microsoft.com/default.aspx?scid=kb;en-us;278918
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"William Holmes" <wthol...@xxxxxxxxxxx> wrote in message
news:ONw$4vWiIHA.3740@xxxxxxxxxxxxxxxxxxxxxxx
I have updated to exchange 2007. However I still have some exchange 2003
objects in my active directory. Is it safe to completely remove these
objects which are all in: CN=First Administrative Group under the
configuration/services container in active directory. There is one
server
in this group, however the server was uninstalled using the exchange
2003
install program so I'm not sure why its still in active directory. Its
presence in AD is causing errors when I run best practices scans. Is
there a specific procedure for removing an orphaned 2003 server from
what
is now an exchange 2007 org.

Thanks

Bill- Hide quoted text -

- Show quoted text -- Hide quoted text -

- Show quoted text -

.

Relevant Pages

  • Re: Email and Sharepoint
    ... After the cooperation works with our WSS and Exchange engineers, ... the URL of the mail server. ... This is a link for public folder web access. ... Go to SharePoint Central Administration page. ...
    (microsoft.public.windows.server.sbs)
  • Re: Email enable doc lib
    ... Please create a email enabled document library to bind a public folder, ... mail server mailbox with Outlook by creating an HTTP mail account"? ... root folder on the Exchange server that hosts public folders. ... The Exchange Virtual Server resolves to that Public/mailbox in IE ...
    (microsoft.public.windows.server.sbs)
  • Re: How to specify an exchange 2003 as remote bridgehead?
    ... We are also planning a year to go to Exchange 2007. ... I think with an administrative group with only RGs, ... Exchange server to their own RG. ... In the Routing Groups container, ...
    (microsoft.public.exchange.admin)
  • RE: Exchange 2003 Public Folder issue - CA XoSoft
    ... get XoSoft off of exchange and go to either E2k7 ccr/scc or some HA ... We are running Exchange 2003 server and CA XoSoft for exchange ... The exchange services on the standby server are ... exchange server public folder store was trying to send system emails to the ...
    (microsoft.public.exchange.misc)
  • Re: Public Folder Replication Problems
    ... How to troubleshoot public folder replication problems in Exchange 2000 ... Server and in Exchange Server 2003 ... Exchange 2000 Server the replication I would assume is supposed to happen ...
    (microsoft.public.exchange2000.general)
Loading