Microsoft Migration accelerator - Process Server NAT?

For the MS MA process server (on premises server), one of the requirements is a NAT setup to an external IP.   Do we have any control over what port the server will be using?  The reason I ask is 80 and 443 on this specific IP are already
consumed and being used for other servers, so I cant NAT those ports to the PS box.
Any insight here would be excellent.  Thanks!

PS server polls to CS server on port 443 for registration and sync the data for reports.
MT server in azure pulls the replication data from process server through ports 9080 and 9443 (If secure options enabled on replications).  MT server will connect to PS server through NAT IP and required ports to be enabled are 9080 and 9443.
Thx-Gopi

Similar Messages

  • Migration Accelerator - Process Server not showing up in CX Configuration

    For the part of the documentation where you establish what the process server is in the CX agent settings. I went to do that setting, but the Process Server never shows up. I have given it a few days and it still doesn't fill in the box.

    Hi Joe,
    This happens when process server is not registered with CS server.  please check below:
    On the Process Server, open
    c:\home\svsystems\etc\AMETHYST.CONF. Search for 'PS_CS_IP' and port.
    please validate above information is correct and PS_CS_IP should be public ip address of CS in Azure and same case for port (it should be public address of CS in Azure). In some cases your public address will change for CS in azure if you shutdown and start 
    the VM. This is due to no reserved IP address configured for this VM.
    if that is the case, you will have to follow below steps to reset the things:
    #1 Reconfigure Source Machine and MT to point to CS
    on the Source Machines and Master Target (in your Azure subscription) you can change it from HOSTCONFIGWXCOMMON.EXE found under <program files>\InMage Systems
    #2 Reconfigure PS to point to CS
    on the Process Server, open c:\home\svsystems\etc\AMETHYST.CONF. Search for 'PS_CS_IP' and change the IP address to point to your new public CS IP address.
    After making changes to your AMETHYST.CONF you need to restart TMANSVC service (go to RUN > services.msc > scroll down to tmansvc & restart it.)
    #3 Reconfigure CS with MA Portal
    Unregister CS from MA from
    From CS Portal > menu Settings > Rx Settings > click ‘Unregister RX’
     Run post deployment script on CS with new public IP as described in HELP, under the section ‘Installation and Configuration’ > ‘Create and Install components’ > ‘Install CS on Windows’ > ‘Run Postdeployconfig script’
    Register CS with MA
    From CS Portal > menu Settings > Rx Settings > click ‘Unregister RX’
    Thx-Gopi

  • [Migration Accelerator] Process Server not recognized in CX.

    Team,
    I have configured CX, MT and PS. When I navigate to Monitor -> Agent Heartbeat; I see "Unknown" value under Machine and Agent Role tab. Looks like I am missing something? Please advice. Many thanks!

    Hi Avihai,<o:p></o:p>
    Problem 1: Machine & Agent role shown Unknown.<o:p></o:p>
    This is normal behavior. This kind of status will be
    shown for Configuration server (CS) & Process server (PS) only.<o:p></o:p>
    You will see the time stamp under "Process Server
    (PS)" only if an server is installed with that role.<o:p></o:p>
    Problem 2:
    Could you please check the 'amethyst.conf'  file in the following location "C:\home\svsystems\etc"
    is provided with the right Configuration server IP (CS).<o:p></o:p>
    PS_CS_IP = "CS_IP"<o:p></o:p>
    PS_CS_PORT = "HTTP/HTTPS_port number"<o:p></o:p>
    Also please check which method of communication is
    selected while installing CS.<o:p></o:p>
    Thanks & Regards,
    Navaharsha Gutta

  • Sign-up for Microsoft Migration Accelerator

    Good morning,
    two days ago we signed up for the preview of Microsoft Migration Accelerator. So far we didn't receive any further information.
    Could you please tell me how long it takes to get a feedback about the sign-up?
    We just want to make sure that we didn't make a mistake during sign-up.
    Thanks,
    Adrian

    Hey Adrian,
    You didn't make any mistake, the migration tool is only available in the US currently.
    It will take sometime.(I registered 2 weeks ago)
    From what I heard it will be one of the big winnings of Microsoft against other Cloud Service Providers as non of them giving you the features that the Microsoft Migration Accelerator will bring.
    Good luck,
    Ido

  • Microsoft Migration Accelerator - Can it be used for cold DR?

    Could we use this tool for cold DR by just keeping it replicating changes and then only turn it on in a disaster? Or is it only for 1 off migrations?

    once you protected your work load whether it is physical or virtual to azure, you can wait for the migration process for few weeks and then just migrate the work load to azure with latest consistency point/time. as we told earlier this preview is just
    for migrations at the moment.
    Thx-Gopi.

  • Migration Accelerator - Public IP address requirement for Config Server and Process Server

    Currently, when installing the Migration Accelerator components, the Config Server's public IP address must be specified in several places.  In the released version of Migration Accelerator, could this be changed to allow customers to specify a public
    DNS domain name instead? Using a Public IP address for the Config Server in Azure represents a risk that this public IP may change (unless using the new Reserved VIP Capability in Azure) which could require reconfiguration of several MA components.  If
    a DNS name will not be supported in the released version of MA, then the documentation should be updated to step through provisioning a Reserved VIP for the Config Server in Azure.
    Similarly, if running the Process Server on Amazon AWS (in an Amazon AWS -> Azure migration scenario), either DNS names should be supported for the Process Server configuration or a reference in the document should be added to step through acquiring an
    Elastic IP Address for the Process Server.

    Thanks Keith for your feedback; we will update the document to reflect this.  We will look into improving this in functionality in the released version.
    Thx - Srinath  

  • Process Server not appearing in Migration Accelerator Portal

    Hi Team,
    I have registered CX portal with RX IP (MA). But still can't see the process server in MA portal discovery agent option.
    If you found this post useful, Please "Mark as Answer" or "Vote as Helpful". Thanks & Regards.

    Hi Joe,
    This happens when process server is not registered with CS server.  please check below:
    On the Process Server, open
    c:\home\svsystems\etc\AMETHYST.CONF. Search for 'PS_CS_IP' and port.
    please validate above information is correct and PS_CS_IP should be public ip address of CS in Azure and same case for port (it should be public address of CS in Azure). In some cases your public address will change for CS in azure if you shutdown and start 
    the VM. This is due to no reserved IP address configured for this VM.
    if that is the case, you will have to follow below steps to reset the things:
    #1 Reconfigure Source Machine and MT to point to CS
    on the Source Machines and Master Target (in your Azure subscription) you can change it from HOSTCONFIGWXCOMMON.EXE found under <program files>\InMage Systems
    #2 Reconfigure PS to point to CS
    on the Process Server, open c:\home\svsystems\etc\AMETHYST.CONF. Search for 'PS_CS_IP' and change the IP address to point to your new public CS IP address.
    After making changes to your AMETHYST.CONF you need to restart TMANSVC service (go to RUN > services.msc > scroll down to tmansvc & restart it.)
    #3 Reconfigure CS with MA Portal
    Unregister CS from MA from
    From CS Portal > menu Settings > Rx Settings > click ‘Unregister RX’
     Run post deployment script on CS with new public IP as described in HELP, under the section ‘Installation and Configuration’ > ‘Create and Install components’ > ‘Install CS on Windows’ > ‘Run Postdeployconfig script’
    Register CS with MA
    From CS Portal > menu Settings > Rx Settings > click ‘Unregister RX’
    Thx-Gopi

  • Problem with migrating data (SQL Server 2k offline data capture)

    Hi there,
    I try to migrate a SQL Server 2000 database to Oracle 10g (R2) using offline data capture. I following the online Tutorial “Migrate from Microsoft SQL Server to Oracle Database 10g Using Oracle Migration Workbench” and everything seems OK until “Migrating the tablespaces, users and user tables to the destination database” http://www.oracle.com/technology/obe/10gr2_db_vmware/develop/omwb/omwb.htm#t5. I have two errors on 2 (out of 85 ) tables saying “ Failed to create default for Table :
    ORA-00907: missing right parenthesis”. I checked the column/table names and they seems OK. I don’t understand why I got these errors. However, when I checked the ‘SA’ Schema in Oracle Enterprise Manager Console, I can see all the tables (including the two problem ones).
    I then carry on to the next step and tried to migrate data to the destination database (http://www.oracle.com/technology/obe/10gr2_db_vmware/develop/omwb/omwb.htm#t6) I am now stuck on step 5. “…copy the files from c:\omwb\data_files to the c:\omwb\Omwb\sqlloader_scripts\SQLServer2K\<timestamp>\Oracle directory…” I cannot find the ‘c:\omwb\data_files’ directory, in fact, I don’t have a directory called ‘data_files’ on my machine. I noticed the ‘c:\omwb\Omwb\sqlloader_scripts\SQLServer2K\<timestamp>\Oracle’ directory contains the all the 85 [tableName].ctl files (plus two other files: ‘sql_load_script’ and ‘sql_load_script.sh’). From the screenshots online, ‘c:\omwb\data_files’ seems contains files with the same name as the [tableName]. Therefore, I did a search with [tableName] but cannot find any apart from the [tableName].ctl file in the ‘c:\omwb\Omwb\sqlloader_scripts\SQLServer2K\<timestamp>\Oracle’ directory. What should I do next?
    OS: windows 2003 with SP1
    Oracle: 10g Release 2
    SQL Server 2000
    Any help would be extremely appreciated.
    Helen

    Helen,
    Sorry, I am new here. Could you please tell me (or point me to the related documents about) how to output the Oracle model as a script?Action-> Generate Migration Scripts
    And what do you mean by ‘The default conversion may have failed’? Do you mean data type mapping? I went through all the columns and tables and checked the data types in the Oracle model already. The processing for the default for a table column could have something the basic workbench default parser cannot handle.
    I hope you are finding the workbench to be a productive aid to migration.
    Regards,
    Turloch
    Oracle Migration Workbench Team

  • 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

  • Error when using Oracle Migration WorkBench (Sql Server 2k to Oracle 8i)

    I'm trying to migrate a Sql Server 2k database to an Oracle 8i schema using OMWB. After using BCP to collect metadata information on the source database, I tried to capture the source data model and got a "Capture aborted" message on the progress screen (even though then it appears a dialog window reporting "0 errors and 0 warnings", funny!). Down there is the error log OMWB generated. After reading some posts, I changed some columns of the OMWB dictionary that holds the source database name, but still got the same error. If someone can enlighten me on this toppic, I'd greatly appreciated it.
    Here's the error log of OMWB:
    ** Oracle Migration Workbench
    ** Production
    ** ( Build 20050629 )
    ** OMWB_HOME: D:\Datos\Download\Oracle\Oracle Migration Workbench\omwb
    ** user language: es
    ** user region: null
    ** user timezone:
    ** file encoding: Cp1252
    ** java version: 1.4.2_04
    ** java vendor: Sun Microsystems Inc.
    ** o.s. arch: x86
    ** o.s. name: Windows 2000
    ** o.s. version: 5.0
    ** Classpath:
    ..\lib\boot.jar
    ** Started : Fri Feb 23 17:18:48 GMT-03:00 2007
    ** Workbench Repository : Oracle8i Enterprise Edition Release 8.1.6.0.0 - Production
    With the Partitioning option
    JServer Release 8.1.6.0.0 - Production
    Repository Connection URL: jdbc:oracle:thin:@ServerCms:1521:sigcewbc
    ** The following plugins are installed:
    ** Microsoft Access 2.0/95/97/2000/2002/2003 Plugin, Production Release 10.1.0.4.0
    ** Microsoft SQLServer 2000 Plugin, Production Release 10.1.0.4.0
    ** Microsoft SQLServer 6.5 Plugin, Production Release 10.1.0.4.0
    ** Microsoft SQLServer 7.0 Plugin, Production Release 10.1.0.4.0
    ** Active Plugin : SQLServer2K
    EXCEPTION :SQLServer2KDisconnSourceModelLoad.loadSourceModel(): oracle.mtg.migration.MigrationStopException: java.lang.IndexOutOfBoundsException: Index: 15, Size: 15
    ** Shutdown : Fri Feb 23 18:00:50 GMT-03:00 2007

    Duplicate thread
    Error when using Oracle Migration WorkBench (Sql Server 2k to Oracle 8i)

  • ODBC Error when migrating from SQL Server 2008 to SQL Anywhere 12

    Hello community,
    i have the following requirement:
    I need to migrate a Database with some Demo data into a SQL Anywhere 12 Database. The SQL Anywhere 12 Database is part of the SAP BusinessObjects Enterprise XI 3.1 SP7 installation and came with the same as OEM Product.
    The Environment looks like the following:
    DB1 is a MS SQL Server 2008 R2 64 Bit running on Windows Server 2008 R2 64 Bit.
    DB2 is the SAP BusinessObjects Enterprise XI 3.1 SP7 installation with the shipped SQL Anywhere 12 (12.0.1.3873) Database running on SLES 11.3 64 Bit
    CL1 is my Windows 7 64 Bit Client where Sybase Central is installed in 64 Bit. On CL1 i have a 64 Bit System ODBC Connection connecting to DB1 successfully.
    Basically i followed the following (pretty straight forward) tutorial:
    Migrating a SQL Server Database to SQL Anywhere White Paper-Technical: Mobile Enterprise, Database Management iAnywhere …
    When i want to test the connection from inside Sybase Central (During the migration process) i receive the following error:
    From inside Sybase Central my connection looks as follows:
    And from the ODBC Manager the connection looks as follows:
    Personally i found is strange that the Sybase ODBC Driver Manager drops the error. I would expect that the MS SQL ODBC Driver Manager pops the error it its related to the ODBC DSN to DB1.
    Any ideas?
    Thanks and Regards
    -Seb.

    Hi Sebastian,
    The data from the SQL Server database must be migrated to an existing SQL Anywhere database.  Could you please tell me where this SQL Anywhere database resides and how are you connecting to it?
    The error message is saying that the connection to the SQL Anywhere remote database server is failing, as opposed to the connection to the SQL Server database.

  • 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

  • Business Rules Migration from one server to other server

    Hi All,
    Can some body help on business rules migration from one server to other server? and also wt is the difference there in Export and import BR's and Administration repository to migrate.........i fail to understand if we export and import br's and need to change in xml target server and after import whether all users can able to see this imported BR's ?
    then wt is the use of Administration option under Business Rules-->right click-->repository...connect--->need to connect oracle info....wt is this process? can some body help on this please........
    thanks,
    huser

    Hi,
    The methods are pretty much the same in what they do.
    When you export rules it creates an xml file based on the selection you have picked, you can just log into EAS and do this you don't have knowledge about the repository, it is also useful for migrating across versions. You also have the option of changing the xml file before importing it into your target.
    When you migrate the respository you have to physically connect to the database repository and have knowledge of the connection details, it is probably aimed directly at a system admin.
    The options in both methods are pretty much the same, you can choose what you want to export or migrate.
    You hit issues when you export/migrate for instance the location names change and need to be updated, you can update the xml file to change the locations though if you choose the migrate option you won't have that ability.
    The next issue is the user/group accounts which is the biggest flaw, if the users/groups exist on the target and have the exact same SID then they will migrate otherwise they will usually get dropped.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Errors in Preview when connecting VMware to Process Server

    Anyone see this when using ASR?  I'm working through this document (http://azure.microsoft.com/en-us/documentation/articles/site-recovery-vmware-to-azure) and getting the below error -
    Job ID: d76cc94a-e4ae-43f6-8f29-23fb2ad15146-2015-04-23 22:35:28Z
    Start Time: 4/23/2015 3:35:28 PM
    Duration: 1 MINUTE
    The operation could not be completed. (Error code: 559)
    Provider error: VCLI is not available to process the ESX discovery on the PS (Provider error code: 2)
    Possible causes: See the provider errors for more information.
    Recommendation: Resolve the issue and retry the operation.
    UTC Time: Thu Apr 23 2015 22:37:25 GMT-0700 (US Mountain Standard Time)
    Browser: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.118 Safari/537.36
    Language: en-us
    Portal Version: 5.3.00298.8 (rd_auxportal_stable.150421-1815)
    PageRequestId: 64a69653-bf53-4168-becf-337651ab81de
    Subscriptions: ec9a0f11-6076-4376-9288-3c3b28b3026b,93e95919-fb64-4df5-b42d-0deee7da6a58

    Hi Robbin,
    Can you please check if you have VMware vSphere CLI 5.5 installed on the process server. If not,please install it and reboot the Process Server. Perform the discovery of Vcenter and let us know how it goes.
    Thanks
    Shashank

  • Migration of Content Server from win2k3 to win2k8

    Hello,
    Now we have installed Conteny Server 6.40 on Windows 2008 server.
    URL check for the Contenet Server is also working.
    We wanted to migrate from Content Server windows 2003 server to Windows 2008 server.
    In the process we have successfully taken the Back up of Content Server on win2k3 server and restored it on win2k8 server.
    Maxdb is the database that we are using.
    Now,i wanted to know what are the steps to be follwoed after the successfull restore.
    How to create Respository and regarding of ContentServer.ini file and security folder settings ( they need to be copied and if yes when?).
    Please help with your suggestions or giving out some referenece documents.
    Thanks,
    deepak

    It depends largely on how you have installed Content Server but if you check the [Operating Manual for SAP Content Server|http://help.sap.com/erp2005_ehp_04/helpdata/EN/8c/e9ddbb5d9a524bbb7854d31b963248/frameset.htm] -> Special Procedures ...it should give enough info for your requirements.
    Nelis

Maybe you are looking for