Configure DTR Client on NWDS

hi all,
would you please advise me on how to configure DTR client on NDWS? My computer has been configured and it works well, but i want to configure DTR client on NDWS on another computer.
Please help me on this. Thanks in advance.
Peerasit

Dear Arun,
please stop posting answers like "search on the internet" and cloning other's answers, as I believe it is unfair, not helpful and makes the SDN threads just longer...
See also "Welcome and Rules of Engagement".
Thank you for your understanding and co-operation
Warm Regards,
Ervin
SAP -- Active Global Support -- NWDI Nexus

Similar Messages

  • How to configure MI client in NWDS

    How to configure MI client in NWDS
    MI home folder
    MI servername: xxxx
    MI webapps TCP  port:
    AWT Runtime
    MI home folder:

    You need not install Tomcat, You have to Install MI client specific to your release.
    <<DO I HAVE TO INSTALL THE MDK PLUGINS OR IT IS INSTALL BY DEFAULT ?>>
    If you have installed NWDS, then by default it consists of MDK also. You have to just configure the MDK Plugin's to work.
    <<where can i download the file that you mentioned in the diagram
    c:\share\MI\MIM2.5SP09JSP>>
    The above path mentioned is just an example, and it need not be same for all.
    Its usually the MI home folder path (You will get this folder once you install the MI client).
    To find the Setup.exe of MI client you can refer to this Link
    Re: need path to download mi client
    Best Regards,
    Lakshmi

  • DTR client disappeared. Need help!

    Hello!
    We had a problem described in Can't connect to DTR. NWDS tries to connect to wrong server We resolved it by running NWDS under another Windows user. But when we tried to work with new track (ESS) we've got another issue: our DTR client for new track has been created successfully but disappeared later! Since DTR client dsappeared we cannot check-in our modifications.
    I found these records in logs:
    !MESSAGE Jun 4, 2009 2:52:11 PM       com.sap.ide.eclipse.component.devconf.DevConfManager     [Thread[main,5,main]] Error: Development Configuration Instantiation failed: C:\Documents and Settings\Администратор\.dtc\1\: DTR client definition not found for this configuration. VFS client-def name: BEP_SANDBOX_D
    !STACK 0
    com.sap.tc.devconf.InvalidDefinitionException: DTR client definition not found for this configuration. VFS client-def name: 'BEP_SANDBOX_D'
         at com.sap.tc.devconf.DevelopmentConfigurationFactory.upgradeLocalConfigurationMode(DevelopmentConfigurationFactory.java:1534)
         at com.sap.tc.devconf.DevelopmentConfigurationFactory.reInitializeConfiguration(DevelopmentConfigurationFactory.java:565)
         at com.sap.tc.devconf.DevelopmentConfigurationFactory._getDevelopmentConfigurationInstance(DevelopmentConfigurationFactory.java:418)
         at com.sap.tc.devconf.DevelopmentConfigurationFactory.getDevelopmentConfigurationInstance(DevelopmentConfigurationFactory.java:197)
         at com.sap.ide.eclipse.component.devconf.DevConfManager.getInstalledDevConfs(DevConfManager.java:411)...
    Why DTR client disappeared? How to resolve it?
    Please help.
    Our NWDS is 7.0.14
    regards, Lev

    Hello,
    Since you read my thread, you already know sometimes the DTR Client configuration is not working really well.
    I don't know if re-starting the NWDS could work.
    Otherwise, your colleague has create an activity and check-in it, so if you want to activate pending activities and have administrator permissions, try:
    1. Log on http://<server-di>:<port-di>/devinf/main as user administrator.
    2. Go to "Component Build Service"
    3. On the top select 'Activities'
    4. Search on the right Buildspace.
    5. There are different Tabs, select "Pending Activities" and filter if needed.
    6. If there, you see the activities, you can select and 'activate' or 'activate even if build fails' it.
    7. You will upload + activate the source code of your colleague and will be able to get it when you sinchronize the DC again from another NWDS.
    The last solution, would be to sinchronize the DC into another user laptop. Then override the local code of your colleague in this new DC. New activity will be ask for changes. Apply changes, check-in and activate.
    Hope it helps.
    Regards,
    David.
    Edited by: David Ruiz de Azúa on Jun 10, 2009 5:32 PM

  • Error while importing configuration from NWDI into NWDS

    Hi All,
    I am working on customizing ESS applications. I am unable to import the configuration from NWDI to NWDS. When I select 'Remote' option and enter the user id and password for SLD, I get the following error:
    <b><b>HTTP response "Unauthorized" from CMS server</b></b>
    Any idea.
    Thanks,
    Tom

    HI Tom,
    Please check your username and password. It iseems it is incorrect.
    Try o login with same id and password on
    http://<server>:<port>/devinf
    Here, try to login on each link. i.e.
    CBS
    CMS
    SLD
    and DTR.
    It will ask for ID and password once again. Check whether it is working here.
    There might be possibilities That you ID is locked.
    Regards,
    Bhavik

  • Automatic DTR Client creation...Please help

    Hello All,
    Am working on NW2004s. While working on NWDI I notifced that a DTR client automatically gets created having name kinda similar to the tracks that are imported.
    Example:
    I have a track named APPL_dev. The automatic DTR client created is named as EPT_APPL_D where,
    EPT is SID
    Question
    1. Is this behavior normal? If yes, does it mean that I should access a track using its associated client?
    2. Does '<b>D</b>' stand for development...<i>seems like but I dont wanna assume</i>.....
    Please help me understand.
    Awaiting Reply.
    Thanks & Warm Regards,
    Ritu

    Hi Ritu,
    in addition to Sidharts reply:
    EPT should be the CMS domain, not necessarily a SID (unless they are equal).
    1. yes, and if you should access the track using the client depends on what you want to do. For normal development you should work in the Development Configuration perspective and the perspective that is relevant for your project types. There  you would see the "APPL_dev" configuration, not the client itself.
    If you need to do DTR operations then you should use that client, although for some operations on DTR a "general" client (not specific to a configuration) is more useful. (E.g. if you want to delete DCs).
    2. Also yes. If you import the "APPL_cons" configuration you should get an EPT_APPL_C client.
    Regards,
    Marc

  • Having issues while configuring JDI/ on my NWDS.

    Having issues while configuring JDI on my NWDS.
    I am logged on to Client's domain. Is there some setting thats required to be done in the hosts/service file which would ensure the same.
    Please advise.

    Hi,
    Can you specify what issues you are facing ?
    Thanks & Regards,
    Meenakshi.

  • SCCM 2012 R2 Configuration Manager Client Package - stuck "In Progress"

    Hi Team; I’m having 2 issues with SCCM 2012 R2:
    Issue 1: I'm having a strange issue with the default XXX00002 package - "Configuration Manager Client Package",
    it will not deploy to the Secondary Site DP. The console is saying "In Progress" - below is the output from the
    distmgr.log file.
    ~Package BDC00002 does not have a preferred sender. 
    $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.443+240><thread=6032 (0x1790)>
    ~CDistributionSrcSQL::UpdateAvailableVersion PackageID=BDC00002, Version=1, Status=2301 
    $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.444+240><thread=6032 (0x1790)>
    ~StoredPkgVersion (1) of package BDC00002. StoredPkgVersion in database is 1. 
    $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.462+240><thread=6032 (0x1790)>
    ~SourceVersion (1) of package BDC00002. SourceVersion in database is 1. 
    $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.462+240><thread=6032 (0x1790)>
    ~Package BDC00003 does not have a preferred sender. 
    $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.443+240><thread=6092 (0x17CC)>
    ~CDistributionSrcSQL::UpdateAvailableVersion PackageID=BDC00003, Version=1, Status=2301 
    $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.464+240><thread=6092 (0x17CC)>
    STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BBK-SCCM-PRI.bbk2310.com SITE=PRI PID=2768 TID=6032 GMTDATE=Mon Mar 17 20:00:23.476 2014
    ISTR0="Configuration Manager Client Package" ISTR1="BDC00002" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="BDC00002" 
    $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.477+240><thread=6032 (0x1790)>
    StateTable::CState::Handle - (2301:1 2014-03-17 20:00:23.476+00:00) >> (0:0 2014-02-28 16:33:45.383+00:00) 
    $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.484+240><thread=6032 (0x1790)>
    CStateMsgReporter::DeliverMessages - Queued message: TT=1401 TIDT=0 TID='8ACCAE01-5079-4FCD-A988-C1CD3004B698' SID=2301 MUF=0 PCNT=2, P1='PRI' P2='2014-03-17 20:00:23.476+00:00' P3='' P4=''
    P5=''  $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.495+240><thread=6032 (0x1790)>
    ~StoredPkgVersion (1) of package BDC00003. StoredPkgVersion in database is 1. 
    $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.496+240><thread=6092 (0x17CC)>
    ~SourceVersion (1) of package BDC00003. SourceVersion in database is 1. 
    $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.497+240><thread=6092 (0x17CC)>
    STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BBK-SCCM-PRI.bbk2310.com SITE=PRI PID=2768 TID=6092 GMTDATE=Mon Mar 17 20:00:23.510 2014
    ISTR0="Configuration Manager Client Upgrade Package" ISTR1="BDC00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400
    AVAL0="BDC00003"  $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.510+240><thread=6092 (0x17CC)>
    StateTable::CState::Handle - (2301:1 2014-03-17 20:00:23.510+00:00) >> (0:0 2014-02-28 16:33:45.383+00:00)
     $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.515+240><thread=6092 (0x17CC)>
    CStateMsgReporter::DeliverMessages - Queued message: TT=1401 TIDT=0 TID='8ACCAE01-5079-4FCD-A988-C1CD3004B698' SID=2301 MUF=0 PCNT=2, P1='PRI' P2='2014-03-17 20:00:23.510+00:00' P3='' P4=''
    P5=''  $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.526+240><thread=6092 (0x17CC)>
    CStateMsgReporter::DeliverMessages - Created state message file: D:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\1sfb1dbj.SMX  
    $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.571+240><thread=6032 (0x1790)>
    Successfully send state change notification 8ACCAE01-5079-4FCD-A988-C1CD3004B698 
    $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.572+240><thread=6032 (0x1790)>
    ~Exiting package processing thread. 
    $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.574+240><thread=6032 (0x1790)>
    CStateMsgReporter::DeliverMessages - Created state message file: D:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\abaibh8y.SMX  
    $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.637+240><thread=6092 (0x17CC)>
    Successfully send state change notification 8ACCAE01-5079-4FCD-A988-C1CD3004B698 
    $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.683+240><thread=6092 (0x17CC)>
    ~Exiting package processing thread. 
    $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.685+240><thread=6092 (0x17CC)>
    Sleep 30 minutes... 
    $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:26.886+240><thread=2936 (0xB78)>
    ~Used 0 out of 3 allowed processing threads. 
    $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:27.948+240><thread=4900 (0x1324)>
    ~Sleep 3600 seconds... 
    $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:27.950+240><thread=4900 (0x1324)>
    Sleep 30 minutes... 
    $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:31.934+240><thread=2936 (0xB78)>
    ~Used 0 out of 3 allowed processing threads. 
    $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:33.021+240><thread=4900 (0x1324)>
    ~Sleep 3600 seconds... 
    $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:33.023+240><thread=4900 (0x1324)>
    ~Used 0 out of 3 allowed processing threads. 
    $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:38.108+240><thread=4900 (0x1324)>
    ~Sleep 3600 seconds... 
    $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:38.111+240><thread=4900 (0x1324)>
    Sleeping for 60 minutes before content cleanup task starts.~ 
    $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:06:28.094+240><thread=4968 (0x1368)>
    Sleep 30 minutes... 
    $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:30:52.271+240><thread=2936 (0xB78)>
    Sleep 30 minutes... 
    $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 17:01:10.002+240><thread=2936 (0xB78)>
    ~Used 0 out of 3 allowed processing threads. 
    $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 17:01:10.977+240><thread=4900 (0x1324)>
    ~Sleep 3600 seconds... 
    $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 17:01:10.979+240><thread=4900 (0x1324)>
    Sleeping for 60 minutes before content cleanup task starts.~ 
    $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 17:06:55.337+240><thread=4968 (0x1368)>
    Issue 2: I'm trying to deploy a couple of Packages/Applications using SCCM 2012 R2 running on Win2K8 R2 with no luck, knowing that I could install the packages
    on a test VM “in the DataCenter site”, but when trying to deploy the packages to production PC “in the Office Site”,
     the status is packages deployment compliance stuck at 0%
    Infrastructure:
    3 SCCM servers: CAS, PRI & SEC. Both CAS and PRI are in the DataCenter site, and SEC is in the Office site. The office site has several IP subnets.
    Boundaries are configured through Forest Discovery “IP Ranges and AD Sites” since that the AD site should contain all the IP subnets that the AD site contains, Boundaries groups are also configured and a site reference
    server is configured for each group respectively.
    A OU based Collection has been configured that contains 13 PC "the collection contains the PCs that the packages should be installed.
    Packages/Applications are configured correctly since that I could successfully deploy the packages to the test VM which is on the same subnet as the CAS and the PRI servers "the DataCenter subnet". The issue
    is that I can't deploy the packages to production PCs in the Office subnet!
    Firewall rules are configured and applied via GP, and I even turned Windows Firewall off, and still nothing! I tried to manually initiate Computer Policy download via the SCCM GUI and via a script, still no luck!
    I tried configuring IP Subnet Boundaries, still no luck!!
    Here are the last 2 lines in the LocationServices.log of a client PC at the Office Site:
    <![LOG[MPLIST requests are throttled for 00:00:44]LOG]!><time="14:47:00.766+240" date="03-17-2014" component="LocationServices" context="" type="2" thread="5776"
    file="lssecurity.cpp:4528"> <![LOG[Current AD site of machine is Default-First-Site-Name]LOG]!><time="14:47:00.777+240" date="03-17-2014" component="LocationServices" context="" type="1"
    thread="4884" file="lsad.cpp:770">
    And here are the last 4 lines in the ClientLocation.log
    <![LOG[Rotating assigned management point, new management point [1] is: BBK-SCCM-PRI.bbk2310.com (7958) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState"
    Value="0"/></Capabilities>]LOG]!><time="14:49:04.880+240" date="03-17-2014" component="ClientLocation" context="" type="1" thread="3600" file="lsad.cpp:6311">
    <![LOG[Assigned MP changed from <BBK-SCCM-PRI.bbk2310.com> to <BBK-SCCM-PRI.bbk2310.com>.]LOG]!><time="14:49:04.891+240" date="03-17-2014" component="ClientLocation" context="" type="1"
    thread="3600" file="lsad.cpp:1532"> <![LOG[Rotating proxy management point, new management point [1] is: BBK-SCCM-SEC.bbk2310.com (7958) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState"
    Value="0"/></Capabilities>]LOG]!><time="14:49:05.345+240" date="03-17-2014" component="ClientLocation" context="" type="1" thread="3600" file="lsad.cpp:6374">
    <![LOG[Rotating local management point, new management point [1] is: BBK-SCCM-SEC.bbk2310.com (7958) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>]LOG]!><time="14:49:05.786+240"
    date="03-17-2014" component="ClientLocation" context="" type="1" thread="3600" file="lsad.cpp:6436">
    It looks like clients in the Office Site can’t connect to the DP/MP of the Secondary Site server which is also a DP.
    While on the PC that the application was installed on I see the folowing in the LocationService.log:
    <![LOG[Distribution Point='http://BBK-SCCM-PRI.bbk2310.com/SMS_DP_SMSPKG$/Content_69547d2a-339f-4ac4-9523-238c79ff8a52.1', Locality='LOCAL', DPType='SERVER', Version='7958', Capabilities='<Capabilities SchemaVersion="1.0"><Property
    Name="SSLState" Value="0"/></Capabilities>', Signature='http://BBK-SCCM-PRI.bbk2310.com/SMS_DP_SMSSIG$/Content_69547d2a-339f-4ac4-9523-238c79ff8a52.1.tar', ForestTrust='TRUE',]LOG]!><time="14:42:59.506+240"
    date="03-17-2014" component="LocationServices" context="" type="1" thread="224" file="lsutils.cpp:415"> <![LOG[Calling back with locations for location request {144620BC-4BF0-4878-9554-F67D305ECCF8}]LOG]!><time="14:42:59.522+240"
    date="03-17-2014" component="LocationServices" context="" type="1" thread="224" file="replylocationsendpoint.cpp:220">
    Is there something wrong with the Distribution point on the Secondary Site server?
    Please help…
    Thanks..

    Update:
    I fixed the issue with the default XXX00002 package - "Configuration Manager Client Package", it will not deploy to the Secondary Site DP. I did that through "Update Distribution Points" option, and after a while the status was 100%.
    However; the second issue is still unsolved...
    Please help..

  • Unable to copy hidden package "Configuration Manager Client Package" to local DP

    Content status lists it as successfully distributed to all DPs (including the local site server)
    However, component status for SMS_DISTRIBUTION_MANAGER continually logs these events:
    Distribution Manager failed to process package "Configuration Manager Client Package" (package ID = CDW00001).
    Possible cause: Distribution manager does not have access to either the package source directory or the distribution point.
    Solution: Verify that distribution manager can access the package source directory/distribution point.
    Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system.
    Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility.
    Possible cause: There is not enough disk space available on the site server computer or the distribution point.
    Solution: Verify that there is enough free disk space available on the site server computer and on the distribution point.
    Possible cause: The package source directory contains files that might be in use by an active process.
    Solution: Close any processes that maybe using files in the source directory. If this failure persists, create an alternate copy of the source directory and update the package source to point to it.
    NOTE: It appears to not be any of these causes.
    If I look at the smsdpmon.log on the server in question, the following is logged every half hour:
    Intializing DP Monitoring Manager...    SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
    Getting monitoring thread priority SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
    Getting content library root path SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
    Getting site code SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
    Getting algorithm ID SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
    Failed to find algorighm ID from registry. Use default algorithm. SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
    Getting DP Cert Type SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
    Failed to find DP cert type from registry. Use default type. SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
    Getting this DP NALPath SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
    Failed to create certificate store from encoded certificate..
    An error occurred during encode or decode operation. (Error: 80092002; Source: Windows) SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
    Failed to initialize DP monitoring object. Error code: 0x80092002 SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
    distmgr.log shows the following:
    STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BRICK-CONFIGMGR.corp.COMPANY.com SITE=CDW PID=2212 TID=2124 GMTDATE=Wed Jan 02 19:29:45.109 2013 ISTR0="CDW00001" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CDW00001"    SMS_DISTRIBUTION_MANAGER    1/2/2013 1:29:45 PM    2124 (0x084C)
    Retrying package CDW00001    SMS_DISTRIBUTION_MANAGER    1/2/2013 1:29:45 PM    2124 (0x084C)
    No action specified for the package CDW00001.    SMS_DISTRIBUTION_MANAGER    1/2/2013 1:29:45 PM    2124 (0x084C)
    Start validating package CDW00001 on server ["Display=\\BRICK-CONFIGMGR.corp.COMPANY.com\"]MSWNET:["SMS_SITE=CDW"]\\BRICK-CONFIGMGR.corp.COMPANYNAME.com\...    SMS_DISTRIBUTION_MANAGER    1/2/2013 1:29:45 PM    2124 (0x084C)
    Failed to start DP health monitoring task for package 'CDW00001'. Error code: -1    SMS_DISTRIBUTION_MANAGER    1/2/2013 1:29:45 PM    2124 (0x084C)
    Updating package info for package CDW00001    SMS_DISTRIBUTION_MANAGER    1/2/2013 1:29:45 PM    2124 (0x084C)
    Only retrying local DP update for package CDW00001, no need to replicate package definition to child sites or DP info to parent site.    SMS_DISTRIBUTION_MANAGER    1/2/2013 1:29:45 PM    2124 (0x084C)
    StoredPkgVersion (2) of package CDW00001. StoredPkgVersion in database is 2.    SMS_DISTRIBUTION_MANAGER    1/2/2013 1:29:45 PM    2124 (0x084C)
    SourceVersion (2) of package CDW00001. SourceVersion in database is 2.    SMS_DISTRIBUTION_MANAGER    1/2/2013 1:29:45 PM    2124 (0x084C)
    STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BRICK-CONFIGMGR.corp.COMPANYNAME.com SITE=CDW PID=2212 TID=2124 GMTDATE=Wed Jan 02 19:29:45.213 2013 ISTR0="Configuration Manager Client Package" ISTR1="CDW00001" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CDW00001"    SMS_DISTRIBUTION_MANAGER    1/2/2013 1:29:45 PM    2124 (0x084C)
    Failed to process package CDW00001 after 41 retries, will retry 59 more times    SMS_DISTRIBUTION_MANAGER    1/2/2013 1:29:45 PM    2124 (0x084C)
    Exiting package processing thread.    SMS_DISTRIBUTION_MANAGER    1/2/2013 1:29:45 PM    2124 (0x084C)
    Used 0 out of 3 allowed processing threads.    SMS_DISTRIBUTION_MANAGER    1/2/2013 1:29:50 PM    3784 (0x0EC8)
    Sleep 1825 seconds...    SMS_DISTRIBUTION_MANAGER    1/2/2013 1:29:50 PM    3784 (0x0EC8)

    Both errors are certificate related. Is there anything special about your configuration such as special ACLs on the certificate store or FIPS compliance mode (see
    http://support.microsoft.com/kb/811833) being enabled?
    Nothing special with certificates; I've used the basic stuff for intranet management of clients.
    The only related thing I can think of that may have affected this, is that I discovered earlier today that my MP installation got hosed (error 500) due to a broken client install on the site server itself. I uninstalled the client manually and the server
    (as indicated by the component status views) appears to have repaired the MP install. Perhaps it didn't repair it completely? Would a site reset do me any good?

  • How to configure dhcp client identifier

    Hi Everybody,
    The DHCP client ID is an id that is unique for DHCP clients at least in the same subnet. Usually the client uses MAC-address as Client-Identifier in the DHCPDISCOVER message. The Client-Identifier may be different other than MAC-Address, For example a FQDN name, as per the RFC 2132 Ref, (code 61).+_
    Usaually, we use the following to bind the ip address based on MAC-address
    pntadm -r SUNWfiles -p /var/dhcp -A 10.42.32.86 -i '0:3:ba:a5:a9:93' -a 10.42.32.80
    At server side, I am using the following for specifying the FQDN name.
    pntadm -r SUNWfiles -p /var/dhcp -A 10.42.32.86 -i 'one.atr.com' -a 10.42.32.80
    and at client side, I am inserting the following entry in the /etc/default/dhcpagent file
    CLIENT_ID='one.atr.com'
    But this is not working. What I am doing wrong.
    +1. At the server side, then how to assign the ip addresses to the clients , if the Client-Identifier is FQDN name in the DHCPDISCOVER message other than MAC-Address.+
    +2. How to configure the client-identifier as FQDN name at client side.+
    Please help me,
    Thanks Inadvance,
    Mummaneni.

    Sandman,
    Here is an example of a router acting as a DHCP server. Please remember that you have to exclude IP addresses that you don't want to lease out.
    ip dhcp pool example
    import all
    network 192.168.1.0 255.255.255.0
    dns-server 1.2.3.4
    default-router 192.168.1.1
    ip dhcp excluded-address 192.168.1.1 192.168.1.149
    ip dhcp excluded-address 192.168.1.200 192.168.1.254
    HTH,
    Mark

  • Why do we need to create DTR client

    Can any one give me some info why DTR client are needed when working with JDI. Because, In NWDI we dont need them...But, now I am workign on older version JDI.. So, can anyone let me know.

    <a href="http://help.sap.com/saphelp_nw04/helpdata/en/83/74c4ce0ed93b4abc6144aafaa1130f/content.htm">This</a> might give you some help you require.
    Regards,
    Shubhadip

  • How do you set up your Configuration Manager client when Imaging?

    OK everyone we got an issue that we need to take care of sorry if this seems like a dumb question but we cant seem to make this work.  How do you set your configuration manager client when you deploy your image(s)?  I created package and pointed
    it right to the config manager install directory just like the recommended one for USMT but it does not seem to work.  I also tried to leave it blank but it appears to be mandatory.. So my question how do YOU get it to work for your areas?
    Thanks

    that might be the problem I dont see a "Microsoft Configuration Manager Client 5.0 All" anywhere. We threw something together that points to:
    \\Server.Domain.com\SCCM_Install\SMSSETUP\CLIENT
    What is happening is this.
    Have a task to deploy Windows natively to the workstation
    Drop applications to the workstation
    do updates
    capture back to server
    All it does is 
    Drop the OS down
    copy the Agent files
    join to the domain
    reboot
    sit
    sit 
    and sit

  • Set Up CTS+:  Webdynpro CTS_BROWSER - configure Organizer client in TMS

    Hi all,
    I'm trying to set up the CTS+ in a Portal Enviroment.
    This is my landscape:
    SID  System Role
    C1X  ABAP + Java Stacks (CTS+ System and Trasport Domain Controller) with SPS15 (ABAP and JAVA)
    JD1  Java Stack (EP Java Development System) Stack SPS14
    JD2  Java Stack (EP Java Production System) Stack SPS14
    I'm following step by step all points of Set Up and Use CTS+ in a Portal Enviroment Guide (May 2008).
    In STMS (C1X) I add JD1 and JD2 System as Non-ABAP-System.
    JD1 is the Java Source system and when I create it I set the flag "Activate Trasport Organizer" for C1X system
    JD2 is the Java Target system and when I create it I set the flag "Activate Deployment Service" for method SDM
    Then I create the new trasport layer ZJAD and the new trasport route from JD1 to JD2.
    When I configure the trasport organizer Web UI and try to test the Web service CTS_BROWSER from SICF I received this message:
    System C1X is not valid; configure Organizer client in TMS
    Any IDEA??
    Could you please help me?
    Thanks
    Moreno

    Hi, I have the same issue here.
    I think that is "normal" because SICF tries to run this in the name of you C1X system. This however must be running in e.g. the name of the development system.
    e.g
    http://hostname:8047/sap/bc/webdynpro/sap/cts_browser?SYSID=<PORTALDEVELPOMENT_SID>&PURPOSE=EP&sap-client=000&sap-language=EN
    Thanks!
    Edited by: BearCheese on Jul 9, 2008 10:05 AM

  • How to configure DTR,CBS and CMS?

    hi all,
           I am working with SneakPreview (EP7.0).Is it possbile to configure DTR,CBS and CMS on sneskpreview ? Can any one tell me the procedure to configure ?
    Thanks&Regards
    Suresh

    Hi,
    pl go through this article
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f37d7e6a-0b01-0010-6690-8f4403b810cf
    Regards
    Ayyapparaj

  • Configuration Manager client upgrade package failing to download to DPs

    Hello,
    I am receiving the following error in distmgr.log "Failed to get RDC signature path for for package SF100004 version 1. Error = 2"
    "SF100004" is the "Configuration Manager client upgrade package"
    Is there a way to rebuild/repair this package? 

    Yes, I did find out how to fix the problem. I had to use a power shell script to call WMI on the site server to manually force a refresh of the package having problems.
    $SiteCode = "SF1"
    $PackageID = "SF100004"
    $distpoints = Get-WmiObject -Namespace "root\SMS\Site_$($SiteCode)" -Query "Select * From SMS_DistributionPoint WHERE PackageID='$PackageID'"
    foreach ($dp in $distpoints)
    $dp.RefreshNow = $true
    $dp.Put()

  • Build and Capture TS fails in "Prepare Configuration Manager Client" task

    I have a ConfigMgr 2012 R2 + CU1 I use for Windows 7 deployment.
    I have made a "build and Capture" TS in ConfigMgr that I use to build my reference image.
    When I run the TS it fails at the "Prepare Configuration Manager Client" step where I get the following error:
    The task sequence execution engine failed executing the action (Prepare Configuration Manager Client) in the group (Capture the Reference Machine) with the error code 2147749938
    Action output: ... 1 instance(s) of 'SMS_MaintenanceTaskRequests' successful
    Successfully reset Registration status flag to "not registered"
    Successfully disabled provisioning mode.
    Start to cleanup TS policy
    getPointer()->ExecQuery( BString(L"WQL"), BString(pszQuery), lFlags, pContext, ppEnum ), HRESULT=80041032 (e:\nts_sccm_release\sms\framework\core\ccmcore\wminamespace.cpp,463)
    ns.Query(sQuery, &spEnum), HRESULT=80041032 (e:\qfe\nts\sms\framework\tscore\utils.cpp,3666)
    End TS policy cleanup
    TS::Utility::CleanupPolicyEx(false), HRESULT=80041032 (e:\nts_sccm_release\sms\client\osdeployment\preparesmsclient\preparesmsclient.cpp,564)
    pCmd->Execute(), HRESULT=80041032 (e:\nts_sccm_release\sms\client\osdeployment\preparesmsclient\main.cpp,136)
    Wmi query 'select *from CCM_Policy where PolicySource = 'CcmTaskSequence'' failed, hr=0x80041032
    Failed to delete policies compiled by TaskSequence (0x80041032)
    Failed to prepare SMS Client for capture, hr=80041032
    Failed to prepare SMS Client for capture, hr=80041032. The operating system reported error 2147942402: The system cannot find the file specified.
    If I disable the "Install Software Updates" part of my TS it will run without probems. It installs 154 updates during the build.
    I have seen another reference to this problem on this forum but why should the large number of the updates be the reason why the task sequcens cannot prepare the SCCM client for capture.
    Sounds to me that it's a BUG :-(
    Thomas Forsmark Soerensen

    I'm glad I'm not the only one running into this.  I've been racking my brain for the past few days trying to figure out where I went wrong. 
    SCCM 2012 R2 CU1
    Installation properties in TS: SMSMP=mp.f.q.d.n FSP=mp.f.q.d.n DNSSUFFIX=f.q.d.n PATCH="%_SMSTSMDataPath%\Packages\AP200003\hotfix\KB2882125\Client\x64\configmgr2012ac-sp1-kb2882125-x64.msp;%_SMSTSMDataPath%\Packages\AP200003\hotfix\KB2905002\Client\x64\configmgr2012ac-r2-kb2905002-x64.msp;%_SMSTSMDataPath%\Packages\AP200003\hotfix\KB2938441\Client\x64\configmgr2012ac-r2-kb2938441-x64.msp"
    Drop Windows 7 WIM that has all the updates Schedule Updates (offline servicing) installed (169 of 277)
    Apply several updates offline (the dual-reboot Windows 7 updates among others)
    Run Windows Updates more than once to be sure I get everything
    Breaks at the preparing client for capture step
    Is this:
    a bug?
    a known issue
    something that's just frowned upon for no technical reason?
    I'd love to hear from an SCCM guru [at Microsoft] on what the heck is going on here.

Maybe you are looking for