Jump to content


IamRichardLucas

Established Members
  • Content Count

    2
  • Joined

  • Last visited

Community Reputation

0 Neutral

About IamRichardLucas

  • Rank
    Newbie
  1. Attached is a diagram I created to understand the type of communication and porst required open for basic SCCM site communication, client communication, and WSUS/SUP. I gathered this information from Technet articles but need verification that it is correct. For example, is it true that if you have WSUS/SUP installed on all of your site servers that they will need ports 8530/8531 to communicate WSUS information to each other or is that handled via SQL replication? Also if client push was used would RCP be required from the secondary to the client? TechNet shows it is but we have not had that port open and have been successful. Is port 80/443 required for any communication between the CAS, primary and secondary site? The client should not need to talk to the WSUS/SUP at the primary if it is available on the secondary so ports 8530/8531 can be closed between the client and the Primary? Would SMB need to be open between the primary and Client if client push is selected to run from the secondary (is this possible)? Anything else you find missing from or needs to be changed in the document? Thank you for the help.
  2. Hello, First I would like to say how wonderful these forums are. This community has already helped me so much that I had to finally sign up. I look forward to participating in discussions moving forward. Today I have a question of my own. I have worked with SCCM for a few years now doing OSD and package deployment and just began building my first SCCM 2007 server at a new company. I took a class dedicated to SCCM 2007 and thought I asked all the right questions but want to verify my migration from SMS 2003 to SCCM 2007 is sound. All Windows XP machines are deployed and managed by SMS2003 at a single AD site. My plan has been to deploy Windows 7 and thus SCCM 2007 configmgr through SCCM2007. As we migrate to Win7 so will the client agents. So I will NOT be upgrading the SMS2003 clients, and the SMS server is NOT a child of the SCCM server (I don’t need any data from it). Both servers have a different site code so as far as I am concerned they are two completely separate environments (which is what I prefer). The only issue I could see is both servers share the same site boundary. The schema in AD has been extended for both SMS and SCCM. I only push the client out during the OSD deployment so they do get the correct site code automatically. The clients get approved automatically (I have had an issue with one or two in testing so far). Will SMS or SCCM clients have unstable communication? It will be difficult to create separate sites as we need to deploy Win7 to test users in different subnets that will overlap with SMS clients. I would prefer not to migrate the winXP machines to the SMS 2007 server. The entire migration should be complete in 6 months. Thank you for your time, Rick
×
×
  • Create New...