Quantcast
Viewing all articles
Browse latest Browse all 6689

CMS 7.6 Deployment Solution

I need a solution

We are currently running 7.1 in production and the last time I played with the product was a 7.5 SP1test system. I don't really remember having many issues in 7.5 SP1

There have, of course, been some minor tweaks in 7.6, making it different from 7.1/7.5 so I am having trouble troubleshooting my issue. Basically, my site server does not seem to be responding to PXE boot. Both Symantec Network Boot Services are running under the local service account. According to: 

https://support.symantec.com/en_US/article.DOC6770...

and my netstat:

C:\Windows\system32>netstat -a

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:80             smp-site1:0            LISTENING
  TCP    0.0.0.0:111            smp-site1:0            LISTENING
  TCP    0.0.0.0:135            smp-site1:0            LISTENING
  TCP    0.0.0.0:445            smp-site1:0            LISTENING
  TCP    0.0.0.0:3389           smp-site1:0            LISTENING
  TCP    0.0.0.0:5985           smp-site1:0            LISTENING
  TCP    0.0.0.0:47001          smp-site1:0            LISTENING
  TCP    0.0.0.0:49152          smp-site1:0            LISTENING
  TCP    0.0.0.0:49153          smp-site1:0            LISTENING
  TCP    0.0.0.0:49154          smp-site1:0            LISTENING
  TCP    0.0.0.0:49155          smp-site1:0            LISTENING
  TCP    0.0.0.0:49166          smp-site1:0            LISTENING
  TCP    0.0.0.0:49203          smp-site1:0            LISTENING
  TCP    0.0.0.0:49204          smp-site1:0            LISTENING
  TCP    0.0.0.0:50124          smp-site1:0            LISTENING
  TCP    127.0.0.1:2049         smp-site1:0            LISTENING
  TCP    172.23.136.244:139     smp-site1:0            LISTENING
  TCP    172.23.136.244:2049    smp-site1:0            LISTENING
  TCP    172.23.136.244:3389    winvm-38:58348         ESTABLISHED
  TCP    172.23.136.244:49254   smp-site1:50124        ESTABLISHED
  TCP    172.23.136.244:50124   smp-site1:49254        ESTABLISHED
  TCP    172.23.136.244:56566   smp-ns1:50123          ESTABLISHED
  TCP    172.23.136.244:56568   172.17.224.18:microsoft-ds  ESTABLISHED
  TCP    172.23.136.244:56569   smp-ns1:microsoft-ds   ESTABLISHED
  TCP    172.23.136.244:56885   fileshare:microsoft-ds  ESTABLISHED
  TCP    172.23.136.244:56897   smp-site1:http         TIME_WAIT
  TCP    172.23.136.244:56898   64.4.54.253:https      ESTABLISHED
  TCP    [::]:80                smp-site1:0            LISTENING
  TCP    [::]:111               smp-site1:0            LISTENING
  TCP    [::]:135               smp-site1:0            LISTENING
  TCP    [::]:445               smp-site1:0            LISTENING
  TCP    [::]:3389              smp-site1:0            LISTENING
  TCP    [::]:5985              smp-site1:0            LISTENING
  TCP    [::]:47001             smp-site1:0            LISTENING
  TCP    [::]:49152             smp-site1:0            LISTENING
  TCP    [::]:49153             smp-site1:0            LISTENING
  TCP    [::]:49154             smp-site1:0            LISTENING
  TCP    [::]:49155             smp-site1:0            LISTENING
  TCP    [::]:49166             smp-site1:0            LISTENING
  TCP    [::]:49203             smp-site1:0            LISTENING
  TCP    [::]:49204             smp-site1:0            LISTENING
  TCP    [::1]:2049             smp-site1:0            LISTENING
  TCP    [fe80::400:92b6:7de0:a4fe%12]:2049  smp-site1:0            LISTENING
  UDP    0.0.0.0:123            *:*
  UDP    0.0.0.0:3389           *:*
  UDP    0.0.0.0:5355           *:*
  UDP    127.0.0.1:111          *:*
  UDP    127.0.0.1:2049         *:*
  UDP    127.0.0.1:49805        *:*
  UDP    127.0.0.1:58914        *:*
  UDP    127.0.0.1:59232        *:*
  UDP    127.0.0.1:59233        *:*
  UDP    127.0.0.1:59686        *:*
  UDP    127.0.0.1:65045        *:*
  UDP    172.23.136.244:67      *:*
  UDP    172.23.136.244:69      *:*
  UDP    172.23.136.244:111     *:*
  UDP    172.23.136.244:137     *:*
  UDP    172.23.136.244:138     *:*
  UDP    172.23.136.244:2049    *:*
  UDP    172.23.136.244:4011    *:*
  UDP    172.23.136.244:64296   *:*
  UDP    [::]:123               *:*
  UDP    [::]:3389              *:*
  UDP    [::]:5355              *:*
  UDP    [::1]:111              *:*
  UDP    [::1]:2049             *:*
  UDP    [fe80::400:92b6:7de0:a4fe%12]:111  *:*
  UDP    [fe80::400:92b6:7de0:a4fe%12]:2049  *:*

I think everything is listening on the right ports, unless I am reading something wrong? When I PXE boot I get an error:

PXE-E53 No boot filename received

According to the Package Server list, I have the BDC, Imaging, DriverDB, Automation Folders, and Deployment Plug-ins on the server. In 7.5, the actual PE image name used to show up, but it's not there now. However, from the NS, I can see the PE image shows a status of being on both site servers. Agent-wise, I have Deployment NBS Plug-in, Deplyment Package Server, Deplyment Task Server Handler installed. In Initial Deployment, I have both options set to run the Boot to PE task, with the Task configured and pointing to the only PE image I have.

I don't remember how things were shared out on previous versions, but if I go to my site servers, I only see:

PkgSvrHostE$

print$

So I am wondering if my shares aren't correctly created/configured, maybe firewall on the server itself (Server 2012r2 comes closed down these days)? OH, I also turned logging to full, and I see that SbsLog_* report errors. These are tested, initially, across VLANs with an iphelper, but to avoid those pitfalls, I still have the issue when on the same subnet as the server. Also, full disclosure, I did not install XML core services, as nothing came up for Server 2012r2, but I did download it incase it became an issue. Also, the account this is running on, is a domain user account with local admin priveleges on all Altiris servers.

Any help appreciated. Thanks


Viewing all articles
Browse latest Browse all 6689

Trending Articles