Anywhere to get 14.2 MP1 (14.2.1057.0103)

[Richard Luxenberg]

We recently upgraded to SEP 14.2.2 and in the process I removed all my old client installation packages. Now, of course, we have some old Windows 2008 servers (not R2) that we need to run and the current SEP client no longer supports Windows 2008.  The last version to do so was 14.2 MP1.  I worked with Broadcom support to try and get a copy of 14.2 MP1, but they insist that they only have 14.2.2 and 14.3 available to download.  Does anyone know where I can find 14.2 MP1 or at least just the client packages?

Thanks,
Rich

[John Owens]

Hi Rich,

What was the case number? I'll try to get those for you tomorrow.

Thanks

[Richard Luxenberg]

Wow, that would be great if you could.  The case number is 32134044

Thanks,
Rich

[Gary_C]

I just spun up and old SEPM VM to see if I had it.  I do and zipped to my OneDrive (all installs including the clients).  Feel free to download from my OneDrive or wait for a Broadcom/Symantec link from John above.
https://healthcentral-my.sharepoint.com/:f:/g/personal/gchilcote_remedyhealthmedia_com/Eng7UQ83XLlNldgJtrFry18BwaCpqHM2Kfxvb5ICXIVwPA?e=TaG7W7

Gary

------------------------------
Gary
------------------------------

[Richard Luxenberg]

Gary,

Thanks so much. I just downloaded the files and will try to get it running later today. I'd be curious to know if John can get it from Broadcom because my case got escalated to a manager and he said that they don't have the older software versions and have no way to get it.  If this is true, it's a huge fail on their part from the symantec purchase because this version is less than a year old and is still officially supported.

Thanks again,
Rich

[Gary_C]

My pleasure.  I put both 14.2 and 14.2 MP1 up in separate downloads.  I've had trouble in the past trying to get old versions, too.

Good luck,
Gary

------------------------------
Gary
------------------------------

[Richard Luxenberg]

Thanks again Gary.  I was able to extract the Agents I needed and install them on the Windows 2008 Server. This support forum gave me the answer in one day after working with Broadcom support for almost a week with no resolution!  I should have come here first :-)

Rich

[Gary_C]

Great to hear.  Yea, we need to help each other out sometimes.  Pay it forward!

------------------------------
Gary
------------------------------

[MIXIT]

Hi Rich, I take it your environment is purely on-prem (but these days, many people confuse SEP and SES hence why I want to be sure here).  But in either case, I would recommend you dig into the recent announcement about requirements to upgrade to 14.3 for SES.  If not done, clients cannot communicate at all with the SES cloud infrastructure because Symantec is moving everything from AWS to GCP, new IP addressing, etc., so pre 14.3 MP1 clients will have no ability to communiate with Symantec servers.  In my SEP environments, where I have all clients set to location-aware LU settings, I imagine when the clients are not on the corporate network they will not be able to report in, get updates, policies, etc.  Unless you have them VPN'd into the network or something, but ugh on that.  
With so much WfH being done, I imagine on-prem isn't 100% likely for client systems, so this presents a problem I suspect.  And per the communication I received, I'm not sure Symantec has factored this in, as there was no mention of what to do if you're a SEP customer having a need to retain older versions.  
So this could be quite a problem for you.  Of course, the bottom line would be that running unsupported OS's is the core problem here, but well, yeah I understand nonetheless :)

[Richard Luxenberg]

MIXIT,

Yes, the servers being secured by SEP are 100% on Prem. We have stuff in the cloud, but this particular data center will be on prem for the foreseeable future. Clearly the answer is to get off the old OS versions that are no longer supported, but in this case, we have a client who is running an old COTS product on a 32-bit Windows 2008 server. Since there's no in-place upgrade path from 32-bit Windows 2008 (all newer Windows OSs are 64-bit) and reinstalling/reconfiguring the COTS product on a new server isn't an option right now, we're stuck with this configuration for now.

Rich

[MIXIT]

Yp that makes sense.  Well hopefully the SEP clients won't travel too much or be WfH :) Else the client might want to spring for a 2nd server or VM instance where a newer SEPM can be installed.