I have added subnet as a boundary in secondary site but still no luck. What is the normal steps that you follow in this scenario? What logs to refer in primary site and in secondary site?
From: [email protected] [mailto:[email protected]] On Behalf Of Bradnan, Jerry Sent: Monday, May 13, 2013 10:57 PM To: [email protected] Subject: [mssms] RE: Secondary Site DP The client may be having trouble finding content and other site information if they are joined to a site. Even if your not using AD sites as a boundary, you still need to define site boundaries for everything to work properly. Use an IP Subnet of IP Range if AD Sites are not available to you. Can you look through the client logs to see if the clients being targeted know where they belong and if they have deployments waiting? Jerry From: [email protected] [mailto:[email protected]] On Behalf Of Surajit Mukherjee Sent: Monday, May 13, 2013 1:03 PM To: [email protected] Subject: [mssms] Secondary Site DP Hi, I have recently installed a new secondary site and wanted to distribute package using the standard DP over there. Data source is on local drive on my primary site server. I have create the package from my primary site and distributed it on secondary site's standard DP. On advertise node I can see the package is installed on DP but the program is not starting on the client machines and in console it is 0. Also I observed the share folders are not getting created on secondary site server where my DP is referred to. I have not created any boundary on my secondary site as we do not have any AD site configured specific to secondary site office location. Any help\guide on this pls. -Surajit The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by forwarding this email to [email protected]<mailto:[email protected]> and then delete it from your system. Ness technologies is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt. The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by forwarding this email to [email protected] and then delete it from your system. Ness technologies is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt.
