Migrating from IIFP + Exchange 2003 to FIM + EXchange 2010

Hello Everyone,
hope you can help me figure something out
i had an IIFP Galsync synchronising users and contacts between 2 exchange 2003 environment and now i would like to switch to fim 2010 and Exchange 2010,
from what i tried just exporting and importing the IIFP configuration to FIM 2010 works, but from what i know exchange 2003 is provisioned through vb code and exchange tools and exchange 2010 through remote powershell, is there anything to change in the
original galsync extension code to enable exchange 2010 provisioning ?
thanks !!
Hitch Bardawil

Hi there Hitch
The old IIFP galsync solution is obviously deprecated now, so I understand why you are wanting to convert it - but there have been too many architectural changes made in each of the components you're targeting to make any kind of conversion exercise realistic.
It is not an overly complicated scenario to handle in FIM, and as you point out the Exchange 2010 platform integration point is totally different and is even built into the MA itself (see
Management Agent for Active Directory Global Address List (GAL)). I suggest you have a trawl through old posts on Carol's blog
to read about her take on what you are trying to do.
Bob Bradley (FIMBob @
TheFIMTeam.com) ... now using FIM Event Broker for just-in-time delivery of FIM 2010 policy via the sync engine, and continuous compliance for FIM

Similar Messages

Migration from an exchange 2003 organisation A (Exchange 2003 sp2) to another Exchange 2010 organisation B

Hello,
We have two Exchange organisations:
- A (Exchange 2003 SP2)
- B (Exchange 2010)
we want to migrate from A to B. the two organisations have to coexist during the migration (6 months). during this time the users have to share the same GAL and Calendar (Busy/Free informations).
What are the steps to follow ?
is there any docs/links treat this subject ?
Regards

Hi,
You can use FIM for GALSYNC.
REF:http://setspn.blogspot.in/2010/05/global-address-list-synchronization-gal.html
For calendar sharing follow the below blog:
REF:http://blogs.technet.com/b/exchange/archive/2011/03/28/iorepl-and-exchange-2010-sp1.aspx
Regards
Vickram

Can't move Exchange 2003 mailbox to Exchange 2010 Resource forest (Linked Mailbox)

Problem Description:
Can’t move Exchange 2003 mailbox to Exchange 2010 resource forest
Error message:
Failed to reconnect to Active Directory server SRVUMVMDC02.umfolozi.local. Make sure the server is available, and that you have used the correct credentials.
Source Environment Configuration:
Active Directory
FQDN: umfolozi.local
Domain name (pre-Windows 2000): UMFOLOZI
Domain Function Level: Windows Server 2003
Domain Controllers:
Hostname
OS
Operation Master
SRVUMVMDC01.umfolozi.local
Windows Server 2008 R2 Standard SP1
Schema Master, Domain Naming, RID, PDC
SRVUMVMDC01.umfolozi.local
Windows Server 2008 R2 Standard SP1
Infrastructure
Exchange
Version: Microsoft Exchange 2003 Standard SP2 Build 7638.2
Server Information:
Hostname
OS
TUSKUMFMAIL.umfolozi.local
Windows Server 2003 R2 SP2
DNS Zones
Zone Name
Zone Type
Domain Controllers
umfolozi.local
Active Directory-Integrated (Primary)
SRVUMVMDC01.umfolozi.local
SRVUMVMDC01.umfolozi.local
peermont.com
Secondary
SRVPGVMDC01.peermont.com
SRVPGVMDC02.peermont.com
Trusts
Domain Name
Trust Type
Transitive
Validated
peermont.com
Forest
Yes
Yes
Target Environment Configuration:
Active Directory
FQDN: peermont.com
Domain name (pre-Windows 2000): PG
Domain Functional Level: Windows Server 2008 R2
Domain Controllers:
Hostname
OS
Operation Master
SRVPGVMDC01.peermont.com
Windows Server 2008 R2 Std SP1
SRVPGVMDC02.peermont.com
Windows Server 2008 R2 Std SP1
Domain naming, RID, PDC, Infrastructure, Schema Master
Exchange
Resource Exchange Forest
Server Information:
Hostname
OS
Role
Version
Client Access Array
SRVPGVMEXCH01.peermont.com
Windows Server 2012 Std
HUB, CAS
Version 14.3 (Build 123.4)
exchange.peermont.com
SRVPGVMEXCH02.peermont.com
Windows Server 2012 Std
HUB, CAS
Version 14.3 (Build 123.4)
exchange.peermont.com
Hostname
OS
Role
Version
Database Availibility Group
SRVPGVMEXCH03.peermont.com
Windows Server 2012 Std
MBX
Version 14.3 (Build 123.4)
PeermontDAG
SRVPGVMEXCH04.peermont.com
Windows Server 2012 Std
MBX
Version 14.3 (Build 123.4)
PeermontDAG
DNS Zones
Zone Name
Zone Type
Domain Controllers
peermont.com
Active Directory-Integrated (Primary)
SRVPGVMDC01.peermont.com
SRVPGVMDC02.peermont.com
umfolozi.local
Secondary
SRVUMVMDC01.umfolozi.local
SRVUMVMDC01.umfolozi.local
Trusts
Domain Name
Trust Type
Transitive
Validated
umfolozi.local
Forest
Yes
Yes
Migration Process
Task
Description
Successful/Error
1
SYNC AD Domain account from source forest (umfolozi.local) to target forest (peermont.com) using BinaryTree SMART Directory Sync (ADMT can be used as alternative)
Successful
2
Create mailed enabled user
Successful
3
Run Prepare-MoveRepuest with –OverWriteLocalObject
Command Example:
.\Prepare-MoveRequest.ps1 -Identity [email protected] -RemoteForestDomainController SRVUMVMDC01.umfolozi.local
-RemoteForestCredential $RemoteCredentials -UseLocalObject -LocalForestDomainController SRVPGVMDC01.peermont.com -LocalForestCredential $LocalCredentials -OverWriteLocalObject
Successful
4
Submit mailbox request
Command Example:
New-MoveRequest -Identity "0fa7d17e-3637-4708-a51b-f14eaae17968" -BadItemLimit "50" -TargetDeliveryDomain
"internal.peermont.com" -TargetDatabase "{c5d6ea95-07b3-4a52-9868-e41e808a76fe}" -RemoteCredential (Get-Credential "umfolozi\svcmigration") -RemoteGlobalCatalog "SRVUMVMDC02.umfolozi.local" -RemoteLegacy:$True
Error
All the standard migration task works as expected until the mailbox migration move request is submitted. See move request verbose detail below:
[PS] C:\Windows\system32>New-MoveRequest -Identity "0fa7d17e-3637-4708-a51b-f14eaae17968" -BadItemLimit "50" -TargetDeli
veryDomain "internal.peermont.com" -TargetDatabase "{c5d6ea95-07b3-4a52-9868-e41e808a76fe}" -RemoteCredential (Get-Crede
ntial "umfolozi\svcmigration") -RemoteGlobalCatalog "SRVUMVMDC02.umfolozi.local" -RemoteLegacy:$True -Verbose
VERBOSE: [11:34:27.346 GMT] New-MoveRequest : Active Directory session settings for 'New-MoveRequest' are: View Entire
Forest: 'False', Default Scope: 'peermont.com', Configuration Domain Controller: 'SRVPGVMDC02.peermont.com', Preferred
Global Catalog: 'SRVPGVMDC02.peermont.com', Preferred Domain Controllers: '{ SRVPGVMDC02.peermont.com }'
VERBOSE: [11:34:27.362 GMT] New-MoveRequest : Runspace context: Executing user: peermont.com/Admin/Users/Admin
Accounts/Information Technology/SoarSoft/Johann Van Schalkwyk, Executing user organization: , Current organization: ,
RBAC-enabled: Enabled.
VERBOSE: [11:34:27.362 GMT] New-MoveRequest : Beginning processing &
VERBOSE: [11:34:27.362 GMT] New-MoveRequest : Instantiating handler with index 0 for cmdlet extension agent "Admin
Audit Log Agent".
WARNING: When an item can't be read from the source database or it can't be written to the destination database, it
will be considered corrupted. By specifying a non-zero BadItemLimit, you are requesting that Exchange not copy such
items to the destination mailbox. At move completion, these corrupted items won't be available in the destination
mailbox.
VERBOSE: [11:34:27.362 GMT] New-MoveRequest : Searching objects "{c5d6ea95-07b3-4a52-9868-e41e808a76fe}" of type
"MailboxDatabase" under the root "$null".
VERBOSE: [11:34:27.362 GMT] New-MoveRequest : Previous operation run on domain controller 'SRVPGVMDC02.peermont.com'.
VERBOSE: [11:34:27.393 GMT] New-MoveRequest : Current ScopeSet is: { Recipient Read Scope: {{, }}, Recipient Write
Scopes: {{, }}, Configuration Read Scope: {{, }}, Configuration Write Scope(s): {{, }, }, Exclusive Recipient Scope(s):
{}, Exclusive Configuration Scope(s): {} }
VERBOSE: [11:34:27.393 GMT] New-MoveRequest : Searching objects "0fa7d17e-3637-4708-a51b-f14eaae17968" of type "ADUser"
under the root "$null".
VERBOSE: [11:34:27.471 GMT] New-MoveRequest : Previous operation run on domain controller 'SRVPGVMDC02.peermont.com'.
VERBOSE: [11:34:27.471 GMT] New-MoveRequest : Processing object "$null".
VERBOSE: [11:34:27.487 GMT] New-MoveRequest : [DEBUG] No RequestJob messages found.
VERBOSE: [11:34:27.487 GMT] New-MoveRequest : [DEBUG] MDB c5d6ea95-07b3-4a52-9868-e41e808a76fe found to belong to Site:
peermont.com/Configuration/Sites/Peermont
VERBOSE: [11:34:27.487 GMT] New-MoveRequest : [DEBUG] MRSClient: attempting to connect to 'SRVPGVMEXCH02.peermont.com'
VERBOSE: [11:34:27.627 GMT] New-MoveRequest : [DEBUG] MRSClient: connected to 'SRVPGVMEXCH02.peermont.com', version
14.3.178.0 caps:07
VERBOSE: [11:34:27.627 GMT] New-MoveRequest : [DEBUG] Loading source mailbox info
VERBOSE: [11:34:28.844 GMT] New-MoveRequest : Failed to reconnect to Active Directory server
SRVUMVMDC02.umfolozi.local. Make sure the server is available, and that you have used the correct credentials. --> A
local error occurred.
VERBOSE: [11:34:28.844 GMT] New-MoveRequest : Admin Audit Log: Entered Handler:OnComplete.
Failed to reconnect to Active Directory server SRVUMVMDC02.umfolozi.local. Make sure the server is available, and that
you have used the correct credentials.
+ CategoryInfo : NotSpecified: (0:Int32) [New-MoveRequest], RemoteTransientException
+ FullyQualifiedErrorId : F48FD74B,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest
+ PSComputerName : srvpgvmexch02.peermont.com
VERBOSE: [11:34:28.859 GMT] New-MoveRequest : Ending processing &
Troubleshooting Performed
1. When submitting mailbox move request tried the following credential inputs:
1.1. DOMAIN\Username
1.2. FQDN\Username
1.3. userPrincipalName
2. Confirmed domain trust between source and target domain is in place and validated.
3. Confirmed name resolution in source and target domain is functioning as expected.
4. Confirmed network connectivity between source and target domain controllers as well as source and target exchange servers.
5. Tried to create new Linked Mailbox to account in source forest, can’t select Global Catologue via the wizard;
Tried to specify the credentials for the account forest and got the following error when tried to select Global Catalog from wizard:

The error talk about the credential. Did you check the credential
Did you tried this command?
New-MoveRequest -Identity "Distinguished name of User in Target Forest" -RemoteLegacy -TargetDatabase "E2K10 Mailbox Database Name" -RemoteGlobalCatalog "FQDN of Source DC" -RemoteCredential $Remote -TargetDeliveryDomain "Target
domain name"
http://blogs.technet.com/b/exchange/archive/2010/08/10/3410619.aspx
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Migrating From Window Server 2003 to Window Server 2012 for Web server deployment and Developmemt Machine is on Window Server 2008

Hi Microsoft Team,
We need your urgent advice and that is also on priority:
Issue Description: We need to migrate from
WINDOW SERVER 2003 to WINDOW SERVER 2012 while the development activity will be carried
under WINDOW SERVER 2008 as DEVELOPMENT BOX.
.NET Framework Version: 3.5 ( For both DEVLOPMENT(WINDOW SERVER 2008) and WEBSERVER(to WINDOW SERVER 2012))
IIS Version: 7.5 (For both DEVLOPMENT(WINDOW SERVER 2008) and WEBSERVER(to WINDOW SERVER 2012))
Need your quick advice Is that configuration feasible for Development and
Deployment (Web Server).
Highly appreciate your response as this will depend which product we need to buy also if you feel any showstopper or concern. Please let us know.

Hi,
As suggested by Tim, in order to get better assistance, we can ask for help in the following IIS forum.
IIS Forum
http://forums.iis.net/
In addition, regarding migrating from Windows Server 2003 to Windows Server 2012, the following blog can be referred to for more information.
Step-By-Step: Active Directory Migration from Windows Server 2003 to Windows Server 2012
http://blogs.technet.com/b/canitpro/archive/2013/05/27/step-by-step-active-directory-migration-from-windows-server-2003-to-windows-server-2012.aspx
Best regards,
Frank Shen

Migration; Exchange 2003 SP2 to Exchange 2013 on new Domain and DC

I wasn't prepared for this task, and it was thrown at me to do... Eyes are bleeding from planning reading and planning, would LOVE any input from you guys. First time posting, here and have heard great things about these forums. The Company
I work for obtained a new client and a network that is in a cluster at the moment, so I'm having to dig through everything and restructure..
Scenario:
Old Domain/Server: (To be decommissioned)
Server 2003 Standard SP2 (Domain: cosco.com; NETBIOS name: coscoex)
Exchange 2003 SP2 (6.5.7638.1)
Server is a domain controller and exchange server.
Migrating to:
Server 2012 R2 Datacenter (New Domain ad.cosco.com; NETBIOS name: cosco)
VM #1: Server 2012 R2 Domain Controller at 2012 R2 Functionality
VM #2: Server 2012 R2 with Exchange 2013 Standard (Not Yet Installed) Joined to ad.cosco.com domain
VM #3: Server 2012 R2 with Exchange 2010 (Not Yet Installed) joined to ad.cosco.com domain
These are probably not ideal conditions, but I have to work with what I'm given.
Host server (2012 R2) is in work group mode. Hyper V Installed with a VM of Server 2012 R2 and as a DC at a functionality level of Server 2012 R2. I had intended starting at a lower functionality level and raising
it later, but.... ya I forgot to change it. If needed I can spool up a new DC with a lower functional level.
DNS, AD and group policy is all jacked up on the 2003 DC so that doesn't matter, All user accounts are going to be created under the new domain. The concern is migrating the mailboxes from Exchange 2003 on the old domain to
Exchange 2013 on the new domain. The client is going to provide CSV of the AD accounts that are still valid (a lot of accounts are no longer used or are from people that no longer with the organization.)
I had some ideas, but I'm not sure if they will work. This is something I have never done before (Senior Engineer Quit).
My thoughts:
- Establish a two way trust relationship between the two domains.
- Create two VM's, one with Exchange 2010 and one with Exchange 2013 (They have a 2010 licence that was not used).
- Create the users on the new domain
- Use the double hop method from Exchange 2003 > Exchange 2010 > Exchange 2013
- Link Exchange accounts to the correct user accounts on the new DC.
Can this be done cleanly? Am I going about this the correct way? Any feedback would be GREATLY appreciated.
Note: We are forced to use ad.cosco.com (Obviously not the actual domain name)

Hi,
Base on my experience, your idea is feasible.
However, before getting started, you should note that Exchange 2010 (with any service pack or update rollups) is not (yet) supported to install on Windows 2012 R2. More details refer to the following link:
http://technet.microsoft.com/library/ff728623(v=exchg.150).aspx
After all the preparations complete, you can refer to the following articles to migration exchange 2003 to 2010, then to 2013:
Exchange 2003 to 2010 Cross-Forest Migration Step by Step Guide
Exchange 2010/2007 to 2013 Migration and Co-existence Guide
Best regards,
Niko Cheng
TechNet Community Support

Migrating from 2003SBS to multi-server 2012 OS/2010 Exchange - what updates are absolutely necessary?

I've got an SBS2003 box that has limited drive space. Aside from the latest Exchange 2003 updates are there any that are absolutely necessary for joining a 2012 R2 DC and Exchange 2010 environment?
I want to keep the updates on the SBS box to an absolute minimum.

Hi:
If your doing a MS migration, the before migration tests should be your guide.
Suggesting it might be better to approach this from the other side. Freeing up space on the SBS 2003 to enable the updates might be a better approach.
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/SBS_Small_Business_Server/A_4475-SBS-2003-System-Drive-Space.html?sfQueryTermInfo=1+30+fl+flyfish
while written for SBS 2008, much of this applies:
http://blogs.technet.com/b/sbs/archive/2010/03/02/recovering-disk-space-on-the-c-drive-in-small-business-server-2008.aspx
Larry Struckmeyer[MVP] If your question is answered please mark the response as the answer so that others can benefit.

Moving Exchange 2003 mailboxes to Exchange 2010

Hello
I have a new domain with Exchange 2010 server. I plan to join users to this domain but would like to know the best plan in moving the existing Exchange 2003 mailboxes over. Can I just import the PST files into their new Exhaneg 2010 mailboxes or is there
a better easier solution?
Thank you

Hi,
You can export mailbox using ExMerge in Exchange 2003, but ExMerge only supports ANSI PST files which have a 2GB limit.
To migrate mailboxes across forests, Active Directory Migration Tool (ADMT) will be used.
Here is a blog which can help you to do cross forest migration from Exchange 2003 to Exchange 2010 for your reference.
Exchange 2010 Cross-Forest Migration Step by Step Guide – Part I
http://blogs.technet.com/b/meamcs/archive/2011/06/10/exchange-2010-cross-forest-migration-step-by-step-guide-part-i.aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2003 sp2 to exchange 2007 sp1 upgrade error

Hi,
We had Windows 2003 DCs and Exchange 2003 servers. We migrated AD DCs to windows 2008 R2 at parent domain.
We have one parent domain and 10 child domains in remote sites .3 remote sites have been migrated to windows 2008 R2.
Now at parent domain I am trying to install exchange 2007 SP1 on a server with windows 2008 R2 SP1. I am facing certain issues:
1. When I run setup /PrepareSchema on this new exchange server , the organization check fails with error stating that : cannot find at least one DC running windows 2003 SP1 or later in DC=xyx,DC=com. This could be the result of moving DC objects in AD. Check
that at least one DC running windows server 2003 SP1 or later is located in the "Domian Controllers" OU and rerun setup".
2. When I try to install exchange server 2007 , I get the following error
Object cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported
by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.".
Can any one shed light on this issue.
Regards
Syed
sa

You cannot install Exchange 2007 SP1 on Windows 2008 R2 SP1 as it is unsupported.
Only version of Exchange 2007 supported when OS is Windows 2008 R2 or R2 SP1 is Exchange 2007 SP3.
Where are you installing Exchange ? child or parent domain ?
2. When I try to install exchange server 2007 , I get the following error "Object
cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.".
Above error indicates that Exchange setup is trying to modify
a version of an object which might have been created when organization is prepared for Exchange 2010. don't you have exchange 2010 Servers already in your environment ?
Please give more information about your current email infrastructure
and whether if you are installing exchange on parent or child domain?
Pavan Maganti ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your
question. ~~ This Information is provided is "AS IS" and confers NO Rights!!

Error while migrating from ms access 2003 db to oracle 10g in sqldeveloper

Hello,
i am working on migration project from MS access 2003 to Oracle 10g on windows XP sp2 plateform using SQL developer.
it went quit smoothly till the "capture microsoft access" .so in this step the sql developer opens the access db in background... but while opening the file in background it gives error
Object library not registered i tried many workaround but of no use..
anybody's help in this regard would be well appreciated.
thanks.

Hi,
Did you follow all the steps in the SQL*Developer documentation about preparing the Access database for migration -
Oracle® SQL Developer User’s Guide Release 3.0 -
2.2.4.3 Before Migrating From Microsoft Access
and -
Oracle® SQL Developer Supplementary Information for Microsoft Access Migrations Release 3.0
2.4 Preparing the Microsoft Access Database for Capture
The error also indicates there may be a problem with your Access installation so could you check that everything is okay with that ? I have found references that indicate a re-install of Office/Access will prevent the error.
Regards,
Mike

ADPrep Migration from Windows Server 2003 to 2012 Foundation Server fails with error 0x80004005

Hi all,
Having a problem the forums and Google have been unsuccessful in helping me with. Server is Windows 2003 R2, migrating to Windows Server 2012 foundation. Have tried the AD Migration on the new 2012 Foundation server both as a standalone server
and a domain server member before running the migration. I get the following error:
ADPrep execution failed --> System.ComponentModel.Win32Exception (0x80004005): A device attached to the system is not functioning
I've checked the ADprep logs and have found the following:
[2013/01/22:11:15:01.000]
Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is cn=abd97102-88dd-4013-a009-0e2c2f967ff6,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=apl,DC=local.
[2013/01/22:11:15:01.001]
LDAP API ldap_search_s() finished, return code is 0x0
[2013/01/22:11:15:01.001]
Adprep checked to verify whether operation cn=abd97102-88dd-4013-a009-0e2c2f967ff6,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=apl,DC=local has completed.
[Status/Consequence]
The operation GUID already exists so Adprep did not attempt to rerun this operation but is continuing.
[2013/01/22:11:15:01.001]
Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is cn=134428a8-0043-48a6-bcda-63310d9ec4dd,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=apl,DC=local.
[2013/01/22:11:15:01.001]
LDAP API ldap_search_s() finished, return code is 0x20
[2013/01/22:11:15:01.001]
Adprep verified the state of operation cn=134428a8-0043-48a6-bcda-63310d9ec4dd,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=apl,DC=local.
[Status/Consequence]
The operation has not run or is not currently running. It will be run next.
[2013/01/22:11:15:01.021]
Adprep was unable to complete because the call back function failed.
[Status/Consequence]
Error message: Unable to access the computer "SERVER.apl.local". The network path was not found.
(0x80070035).
[User Action]
Check the log file ADPrep.log, in the C:\Windows\debug\adprep\logs\20130122111500 directory for more information.
DSID Info:
DSID: 0x1811132a
winerror = 0x1f
NT BUILD: 9200
NT BUILD: 16384
[2013/01/22:11:15:01.021]
Adprep was unable to update forest information.
[Status/Consequence]
Adprep requires access to existing forest-wide information from the schema master in order to complete this operation.
[User Action]
Check the log file, ADPrep.log, in the C:\Windows\debug\adprep\logs\20130122111500 directory for more information.
We did have AVAST Antivirus installed on the server but this was removed. Any idea's?
Jason.
Consultant | Nerd | Visionary. http://www.ethertech.com.au/ | http://www.deeperstates.com.au

Hi Biswajit et. al., thanks for your help thus far, it is greatly appreciated...
Unfortunately I had already disabled the NIC's on both hosts. They currently remain disabled. I've just tried turning off IPv6 as well and no luck.
PortQry came back fine (I think) :)
=============================================
Starting portqry.exe -n server.apl.local -e 135 -p TCP ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
TCP port 135 (epmap service): LISTENING
Using ephemeral source port
Querying Endpoint Mapper Database...
Server's response:
UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint
ncalrpc:[dhcpcsvc]
UUID: f1ec59ab-4ca9-4c30-b2d0-54ef1db441b7 Isolation Communication Endpoint
ncalrpc:[LRPC00001d40.00000001]
UUID: f1ec59ab-4ca9-4c30-b2d0-54ef1db441b7 Isolation Communication Endpoint
ncalrpc:[LRPC00001448.00000001]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[OLE4EF57D32A0DB45F9A64653468D7C]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC000012ac.00000001]
UUID: 2f5f6521-cb55-1059-b446-00df0bce31db Unimodem LRPC Endpoint
ncacn_np:\\\\SERVER[\\pipe\\tapsrv]
UUID: 2f5f6521-cb55-1059-b446-00df0bce31db Unimodem LRPC Endpoint
ncalrpc:[tapsrvlpc]
UUID: 2f5f6521-cb55-1059-b446-00df0bce31db Unimodem LRPC Endpoint
ncalrpc:[unimdmsvc]
UUID: 3473dd4d-2e88-4006-9cba-22570909dd10 WinHttp Auto-Proxy Service
ncalrpc:[W32TIME_ALT]
UUID: 3473dd4d-2e88-4006-9cba-22570909dd10 WinHttp Auto-Proxy Service
ncacn_np:\\\\SERVER[\\PIPE\\W32TIME_ALT]
UUID: 6bffd098-a112-3610-9833-46c3f874532d
ncalrpc:[OLE7C4E3B9B79D8492CBA384F149E08]
UUID: 6bffd098-a112-3610-9833-46c3f874532d
ncacn_ip_tcp:10.0.0.3[1111]
UUID: 6bffd098-a112-3610-9833-46c3f874532d
ncalrpc:[DHCPSERVERLPC]
UUID: 5b821720-f63b-11d0-aad2-00c04fc324db
ncalrpc:[OLE7C4E3B9B79D8492CBA384F149E08]
UUID: 5b821720-f63b-11d0-aad2-00c04fc324db
ncacn_ip_tcp:10.0.0.3[1111]
UUID: 5b821720-f63b-11d0-aad2-00c04fc324db
ncalrpc:[DHCPSERVERLPC]
UUID: 3d267954-eeb7-11d1-b94e-00c04fa3080d
ncalrpc:[LRPC00000480.00000001]
UUID: 3d267954-eeb7-11d1-b94e-00c04fa3080d
ncacn_np:\\\\SERVER[\\pipe\\HydraLsPipe]
UUID: 3d267954-eeb7-11d1-b94e-00c04fa3080d
ncacn_ip_tcp:10.0.0.3[1092]
UUID: 12d4b7c8-77d5-11d1-8c24-00c04fa3080d
ncalrpc:[LRPC00000480.00000001]
UUID: 12d4b7c8-77d5-11d1-8c24-00c04fa3080d
ncacn_np:\\\\SERVER[\\pipe\\HydraLsPipe]
UUID: 12d4b7c8-77d5-11d1-8c24-00c04fa3080d
ncacn_ip_tcp:10.0.0.3[1092]
UUID: 493c451c-155c-11d3-a314-00c04fb16103
ncalrpc:[LRPC00000480.00000001]
UUID: 493c451c-155c-11d3-a314-00c04fb16103
ncacn_np:\\\\SERVER[\\pipe\\HydraLsPipe]
UUID: 493c451c-155c-11d3-a314-00c04fb16103
ncacn_ip_tcp:10.0.0.3[1092]
UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe
ncalrpc:[OLE43978C47C6F54B5499302BAB2F50]
UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe
ncacn_ip_tcp:10.0.0.3[1090]
UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe
ncalrpc:[LRPC00001060.00000001]
UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe
ncacn_np:\\\\SERVER[\\pipe\\WinsPipe]
UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45
ncalrpc:[OLE43978C47C6F54B5499302BAB2F50]
UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45
ncacn_ip_tcp:10.0.0.3[1090]
UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45
ncalrpc:[LRPC00001060.00000001]
UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45
ncacn_np:\\\\SERVER[\\pipe\\WinsPipe]
UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
ncalrpc:[OLE92F283EA5C2F497093CE6A52B7D8]
UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
ncacn_ip_tcp:10.0.0.3[1067]
UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
ncalrpc:[LRPC00000d10.00000001]
UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
ncalrpc:[OLE92F283EA5C2F497093CE6A52B7D8]
UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
ncacn_ip_tcp:10.0.0.3[1067]
UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
ncalrpc:[LRPC00000d10.00000001]
UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
ncalrpc:[OLE92F283EA5C2F497093CE6A52B7D8]
UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
ncacn_ip_tcp:10.0.0.3[1067]
UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
ncalrpc:[LRPC00000d10.00000001]
UUID: 50abc2a4-574d-40b3-9d66-ee4fd5fba076
ncacn_ip_tcp:10.0.0.3[1048]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC000004d4.00000001]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncacn_ip_tcp:10.0.0.3[1032]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC000004d4.00000001]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncacn_ip_tcp:10.0.0.3[1032]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC000004d4.00000001]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncacn_ip_tcp:10.0.0.3[1032]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC000004d4.00000001]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncacn_ip_tcp:10.0.0.3[1032]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_np:\\\\SERVER[\\PIPE\\lsass]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[audit]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[securityevent]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[protected_storage]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[dsrole]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_ip_tcp:10.0.0.3[1026]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[NTDS_LPC]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_http:10.0.0.3[1027]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_np:\\\\SERVER[\\PIPE\\lsass]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[audit]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[securityevent]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[protected_storage]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[dsrole]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_ip_tcp:10.0.0.3[1026]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[NTDS_LPC]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_http:10.0.0.3[1027]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_np:\\\\SERVER[\\PIPE\\lsass]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[audit]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[securityevent]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[protected_storage]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[dsrole]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_ip_tcp:10.0.0.3[1026]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[NTDS_LPC]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_http:10.0.0.3[1027]
UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncacn_np:\\\\SERVER[\\PIPE\\lsass]
UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncalrpc:[audit]
UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncalrpc:[securityevent]
UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncalrpc:[protected_storage]
UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncalrpc:[dsrole]
UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncacn_ip_tcp:10.0.0.3[1026]
UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncalrpc:[NTDS_LPC]
UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncacn_http:10.0.0.3[1027]
UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncacn_np:\\\\SERVER[\\PIPE\\lsass]
UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncalrpc:[audit]
UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncalrpc:[securityevent]
UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncalrpc:[protected_storage]
UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncalrpc:[dsrole]
UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncacn_ip_tcp:10.0.0.3[1026]
UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncalrpc:[NTDS_LPC]
UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncacn_http:10.0.0.3[1027]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_np:\\\\SERVER[\\PIPE\\lsass]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[audit]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[securityevent]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[protected_storage]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[dsrole]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_ip_tcp:10.0.0.3[1026]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[NTDS_LPC]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_http:10.0.0.3[1027]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncacn_np:\\\\SERVER[\\PIPE\\lsass]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncalrpc:[audit]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncalrpc:[securityevent]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncalrpc:[protected_storage]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncalrpc:[dsrole]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncacn_ip_tcp:10.0.0.3[1026]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncalrpc:[NTDS_LPC]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncacn_http:10.0.0.3[1027]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncalrpc:[OLE8B33809919104CE5B44970B01637]
UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncalrpc:[wzcsvc]
UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncalrpc:[OLE396AE4FBEFCC4DD2B44D0F0A3691]
UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncacn_np:\\\\SERVER[\\PIPE\\atsvc]
UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncalrpc:[wzcsvc]
UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncalrpc:[OLE396AE4FBEFCC4DD2B44D0F0A3691]
UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncacn_np:\\\\SERVER[\\PIPE\\atsvc]
UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53
ncalrpc:[wzcsvc]
UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53
ncalrpc:[OLE396AE4FBEFCC4DD2B44D0F0A3691]
UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53
ncacn_np:\\\\SERVER[\\PIPE\\atsvc]
UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint
ncalrpc:[DNSResolver]
Total endpoints found: 125
==== End of RPC Endpoint Mapper query response ====
portqry.exe -n server.apl.local -e 135 -p TCP exits with return code 0x00000000.
=============================================
Starting portqry.exe -n server.apl.local -e 389 -p BOTH ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
TCP port 389 (ldap service): LISTENING
Using ephemeral source port
Sending LDAP query to TCP port 389...
LDAP query response:
currentdate: 01/28/2013 14:11:54 (unadjusted GMT)
subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=apl,DC=local
dsServiceName: CN=NTDS Settings,CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
namingContexts: DC=apl,DC=local
defaultNamingContext: DC=apl,DC=local
schemaNamingContext: CN=Schema,CN=Configuration,DC=apl,DC=local
configurationNamingContext: CN=Configuration,DC=apl,DC=local
rootDomainNamingContext: DC=apl,DC=local
supportedControl: 1.2.840.113556.1.4.319
supportedLDAPVersion: 3
supportedLDAPPolicies: MaxPoolThreads
highestCommittedUSN: 1310788
supportedSASLMechanisms: GSSAPI
dnsHostName: SERVER.apl.local
ldapServiceName: apl.local:[email protected]
serverName: CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
supportedCapabilities: 1.2.840.113556.1.4.800
isSynchronized: TRUE
isGlobalCatalogReady: TRUE
domainFunctionality: 2
forestFunctionality: 2
domainControllerFunctionality: 2
======== End of LDAP query response ========
UDP port 389 (unknown service): LISTENING or FILTERED
Using ephemeral source port
Sending LDAP query to UDP port 389...
LDAP query response:
currentdate: 01/28/2013 14:11:57 (unadjusted GMT)
subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=apl,DC=local
dsServiceName: CN=NTDS Settings,CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
namingContexts: DC=apl,DC=local
defaultNamingContext: DC=apl,DC=local
schemaNamingContext: CN=Schema,CN=Configuration,DC=apl,DC=local
configurationNamingContext: CN=Configuration,DC=apl,DC=local
rootDomainNamingContext: DC=apl,DC=local
supportedControl: 1.2.840.113556.1.4.319
supportedLDAPVersion: 3
supportedLDAPPolicies: MaxPoolThreads
highestCommittedUSN: 1310788
supportedSASLMechanisms: GSSAPI
dnsHostName: SERVER.apl.local
ldapServiceName: apl.local:[email protected]
serverName: CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
supportedCapabilities: 1.2.840.113556.1.4.800
isSynchronized: TRUE
isGlobalCatalogReady: TRUE
domainFunctionality: 2
forestFunctionality: 2
domainControllerFunctionality: 2
======== End of LDAP query response ========
UDP port 389 is LISTENING
portqry.exe -n server.apl.local -e 389 -p BOTH exits with return code 0x00000000.
=============================================
Starting portqry.exe -n server.apl.local -e 636 -p TCP ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
TCP port 636 (ldaps service): LISTENING
portqry.exe -n server.apl.local -e 636 -p TCP exits with return code 0x00000000.
=============================================
Starting portqry.exe -n server.apl.local -e 3268 -p TCP ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
TCP port 3268 (msft-gc service): LISTENING
Using ephemeral source port
Sending LDAP query to TCP port 3268...
LDAP query response:
currentdate: 01/28/2013 14:11:57 (unadjusted GMT)
subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=apl,DC=local
dsServiceName: CN=NTDS Settings,CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
namingContexts: DC=apl,DC=local
defaultNamingContext: DC=apl,DC=local
schemaNamingContext: CN=Schema,CN=Configuration,DC=apl,DC=local
configurationNamingContext: CN=Configuration,DC=apl,DC=local
rootDomainNamingContext: DC=apl,DC=local
supportedControl: 1.2.840.113556.1.4.319
supportedLDAPVersion: 3
supportedLDAPPolicies: MaxPoolThreads
highestCommittedUSN: 1310788
supportedSASLMechanisms: GSSAPI
dnsHostName: SERVER.apl.local
ldapServiceName: apl.local:[email protected]
serverName: CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
supportedCapabilities: 1.2.840.113556.1.4.800
isSynchronized: TRUE
isGlobalCatalogReady: TRUE
domainFunctionality: 2
forestFunctionality: 2
domainControllerFunctionality: 2
======== End of LDAP query response ========
portqry.exe -n server.apl.local -e 3268 -p TCP exits with return code 0x00000000.
=============================================
Starting portqry.exe -n server.apl.local -e 3269 -p TCP ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
TCP port 3269 (msft-gc-ssl service): LISTENING
portqry.exe -n server.apl.local -e 3269 -p TCP exits with return code 0x00000000.
=============================================
Starting portqry.exe -n server.apl.local -e 53 -p BOTH ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
TCP port 53 (domain service): LISTENING
UDP port 53 (domain service): LISTENING
portqry.exe -n server.apl.local -e 53 -p BOTH exits with return code 0x00000000.
=============================================
Starting portqry.exe -n server.apl.local -e 88 -p BOTH ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
TCP port 88 (kerberos service): LISTENING
UDP port 88 (kerberos service): LISTENING or FILTERED
portqry.exe -n server.apl.local -e 88 -p BOTH exits with return code 0x00000002.
=============================================
Starting portqry.exe -n server.apl.local -e 445 -p TCP ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
TCP port 445 (microsoft-ds service): LISTENING
portqry.exe -n server.apl.local -e 445 -p TCP exits with return code 0x00000000.
=============================================
Starting portqry.exe -n server.apl.local -e 137 -p UDP ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
UDP port 137 (netbios-ns service): LISTENING or FILTERED
Using ephemeral source port
Attempting NETBIOS adapter status query to UDP port 137...
Server's response: MAC address 000423c733ec
UDP port: LISTENING
portqry.exe -n server.apl.local -e 137 -p UDP exits with return code 0x00000000.
=============================================
Starting portqry.exe -n server.apl.local -e 138 -p UDP ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
UDP port 138 (netbios-dgm service): LISTENING or FILTERED
portqry.exe -n server.apl.local -e 138 -p UDP exits with return code 0x00000002.
=============================================
Starting portqry.exe -n server.apl.local -e 139 -p TCP ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
TCP port 139 (netbios-ssn service): LISTENING
portqry.exe -n server.apl.local -e 139 -p TCP exits with return code 0x00000000.
=============================================
Starting portqry.exe -n server.apl.local -e 42 -p TCP ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
TCP port 42 (nameserver service): LISTENING
portqry.exe -n server.apl.local -e 42 -p TCP exits with return code 0x00000000.
Jason.
Consultant | Nerd | Visionary. http://www.ethertech.com.au/ | http://www.deeperstates.com.au

Migration from MS Access 2003

Hello,
I'm very new to MS SQL Server; I just downloaded Express 2005 yesterday. I have it up and running; it seems to be working fine.
Now onto business - I need to migrate data from existing MS Access 2003. How, exactly, do I do this? I've tried searching MSDN, TechNet, and here, and while I get results that seem to tell part of the story, I don't seem to get a true "How to" for this task.
Can someone please assist me with this?
Thank you.

Hello,
I'm very new to MS SQL Server; I just downloaded Express 2005 yesterday. I have it up and running; it seems to be working fine.
Now onto business - I need to migrate data from existing MS Access 2003. How, exactly, do I do this? I've tried searching MSDN, TechNet, and here, and while I get results that seem to tell part of the story, I don't seem to get
a true "How to" for this task.
Can someone please assist me with this?
Thank you.
If you are trying to migrate complete database then refer
Woody's link. We can also use Import Export Wizard/Linked Server/OpenRowSet to import data from MS Access Database to SQL Server database.
References
http://technet.microsoft.com/en-us/library/ms190312.aspx
http://www.mssqltips.com/sqlservertip/1480/configure-microsoft-access-linked-tables-with-a-sql-server-database/
http://technet.microsoft.com/en-us/library/ms140052.aspx
Regards, RSingh

Migrate From MS Access 2003 to Oracle using Oracle SQL Developer 3.0

Hello All,
I am trying to migrate Access DB .mdb using the Oracle SQL Dev 3.0 Data Migration Wizard, everything go very nice and smooth until the Capture Step, for sure am using the online mode, in the Capture Step the list of available databases is empty and a Msg Box saying that the DB list should have at leats one database selected, so I don't know what's that mean or how to fix this.
in my .mdb file I have four tables and I can copy the data to Oracle using the Right click and copy to Oracle Function, but it really takes much time.
Any help would be really appreciated and thanks in advance.
yours,
Hussein

Just to clarify:
You have created the migration repository and start the migration using Tools => Migration => Migrate
- now you've selected the repositiry
- specified a project
- selected the source database
=> you've choosen the ONLINE Mode
==>> and now you don't see your MS Access database in the "Connection" List
Is this correct?
If the steps you're doing match the steps I've posted above, then please be aware for MS Access migrations you need to choose the OFFLINE method. The MS Access source database information is collected by the MS Access Exporter available from Tools => Migration => MS Access Exporter
Once you've created the XML/OCP file you specify this newly created file during the OFFLINE migration mode.
If your steps differ from mine, please post yours more detailed.
Thx.

Migrate from x64 to 2003 standard

I have a moss 2007 site setup with lots of content and subsites. I need to move it from the 2003 x64 nos to another server that will be 2003 standard server. Both will use the msde db. I tried the internal backup/restore but that blew up big time.
So...I want to retain the sites, layouts, content, and site settings if possible.

Hi,
What is the type of SharePoint installation i.e. Standalone installation or Farm installation or Single server(SQL and SharePoint on same box)?

Exchange 2003, SBS Server, Outlook 2010, User Over Limit, 2 GIgs

I have a user's who's account is over limit. I have recently done a clean install of Windows 7 Professional and Office 2010. I keep trying to have his computer archive old emails but in the process the machine keeps hanging. I try to crash out Outlook
but the outlook.exe process will not let me shut it down telling me access denied. The only way to recover is to completely shut down the computer (which I cannot do VIA the regular shutdown option because of outlook hanging). What do I have to do to resolve
this problem? Kind of urgent as it's affecting his receiving emails.
Vern

Hello,
According to your description, the issue seems to be related to outlook profile or your PC. I recommend you check if the issue occurs when other users use the PC. If the issue doesn't occurs, it means your outlook profile should be problem.
If the issue persists, please check if there is related error in application log.
If there is any update, please free let me know.
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Exchange 2003 to 2010

I want to migrate from a Windows 2003 server with Exchange 2003 to a Windows 2012 Server with Exchange 2010. My question is when installing Exchange 2010 on the Windows 2012 server does the Exchange server need to be part of the existing Exchange
environment or installed as a stand alone Exchange server?

Hi,
You can install Exchange 2010 in an existing Exchange 2003 organization.
Here is an article about how to install Exchange 2010 in an existing Exchange 2003 organization for your reference.
Install Exchange 2010 in an Existing Exchange 2003 Organization
More information:
Upgrade Exchange 2003 to Exchange 2010
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
Hope this helps.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Migrating from IIFP + Exchange 2003 to FIM + EXchange 2010

Similar Messages

Maybe you are looking for