Endpoint Protection

Has anyone tried loading SEP 11 on Windows 7 RC.  I am just starting to load up some test machines and wanted to know if there is anything special to watch for.

 

I have MR4MP1A running on Windows 7 RC x64 with no problems other than the installation took a long time compared to XP (auto protect was turned off and the client said I had AV definition failures).  I just left the computer running for an hour or so (note, I was installing Office, Microsoft updates and other software at the same time).  All problems cleared up once all of my software installations finished.

Same as Rick except running on 32bit version on VMWare PC.
No issue so far, but only a day into it.
All defs and policies updated themselves from the SEM server.

Note that this is not claiming that you won't have issues nor is it stating that you will - just that you asked, and I relplied it's running and working here so far.  ;-)

Can't speak to the Device Control (installed on a 64-bit system), but it's been working as a managed anti-virus / anti-spyware client since build 7000.  Now running on the RC, which was upgraded from build 7077.  No hiccups to date.

Had to reboot my Win 7 RC box and I no longer have the green dot.  Help/Troubleshooting shows my server (does not say offline).  On the SEPM, it shows a green dot on for my computer and last check in was 5 minutes ago (rebooted over 15 minutes ago).  Tried updating the policy from the client.  Netstat shows I have an established connection with the server over port 8570 (yes, it's a custom port) from the smc.exe process.  Must be just a cosmetic flaw....

EDIT: Client Management System log says I am connected to my SEPM and even applied my location policy

2nd EDIT: Rebooted again and the green dot is back

Going to try out SEP 12 on a Win 7 test machine this weekend. I will let you know how it goes too.

Still using without any problem.

I have it loaded on build 7100 64 bit at the moment and I am seeing erros in how it reports to windows.  Windows knows that SEP is there but it is reporting in a method that is nolonger supported says please contact your vendor to have them update the program.   After running live update that goes away and no it thinks that symantec is out of date even though definitions are dated Monday May 4 r41 which is what my other machines are showing

yep, I noticed that last night.  I think its fixed in the later version we have internally (I didn't notice it last time I checked)... it will certainly be fixed in MR5, which will be the point at which we officially support and test the product.

LOL - just totally trashed our Win7 machine!
Yes, it's trashed, won't boot normally, keeps stating it needs to repair itself.
This task that so totally trashed it beyond repair?
MICROSOFT UPDATES!
It wasn't even SEP that killed it. It was Microsofts own updates.
So we start over........... too bad I didnt' make a snapshot first - my bad, but who'd have thunk?

Any idea a time frame being targeted for MR5?   I am guessing the we will see Win 7 RTM this summer some time and I want to get a working build of it on test users ASAP.

At the moment, August, that might change though.

Our plan (as standard) is to release a version offiically supporting Windows 7 within 30 days of W7 launch

I like hearing short time frames like that especially from a Microsoft partner.  I have little tolerance for  a Software Vendor that is a micosoft partner and says something like 6 months to a year from when it releases.  Even worse if they dont start developing or testing until it releases.
 

What do you concider launch thought RTM or when it hits the big box stores?  I can understand meaning when it hits the big box stores. 

I loaded SEP MR4 on my Windows 7 RC install, and after a reboot it kept blue screening. Fortunately Windows 7 has a nice feature that instead of actually showing the blue screen, it came up with a GUI wizard to resolve the startup problems. In my case, that meant rolling back to the system restore point prior to loading SEP. Now I had more SEP components selected than just the AV component, so that may have been the culprit. I haven't tried it yet with only the AV component loaded.

Shadows,

Do you know what updates killed your Win7 installation?  The first thing I did after installing SEP was to run MS updates and installed all updates without problems.  Just curious.

J.Bonner, FWIW, I selected all components to install but only AV/AS and PTP installed and all is working fine.

If you are still installing MR4 onto RC, then please don't.

Make sure you are using MR4 MP1a.  Everything is working here (apart from the Security Center notification)

@Rick, personally I would consider "launch" to be RTM, or when it hits MSDN/Technet, etc.

I would have to confirm our official definition though, I expect it would be sometime between then and when the boxed product hits the shelves.

Same here, it trashed my test box.

Keeps rebooting, until I do a restore point. Its not happy with MR4

are you using MR4, or MR4 MP1a?

 Seems that the "sandbox" conflict is back in Windows 7 x64 RC + SEP 11 MR4 MP1a (11.0.4014) + Google Chrome. Chrome runs fine on Windows 7 by itself, but as soon as I install SEP, Chrome breaks and I have to run it with the -no-sandbox shortcut.

Any feedback on this?

I was using MR4 MP1a.

Hi all,

I had to search the board to see if anyone else was having this problem because I reported it a week ago and had no response on the blogs here.

Anyway, The system worked fine until I installed SEP. Now it just reboots constantly. I uninstalled SEP and the system is working fine again.

Now i'm running the latest version of SAV and holding out until the SEPcompatible version is available.

Thank you,

~Brett A. Scudder~

I had two small issues with the install:
Windows firewall, even on our LAN, is a pain for the push.
SEPM lists the machine as a Vista Ultimate client.. :)

This was using MR4MP1a

My guess on why it miss reports it as Vista Ultimate client is that it problably looks at the version number of windows and that is the closest thing to a match.   I am betting that it will be fixed in the next build as they probably added the intelegince to pick up windows 7.  At least I hope they did.  I have to say over all I like Windows 7 so far.

Is it normal that network threat protection is disabled when installed on Win 7? I installed normally with all options (MR4 MP1a), but I don't see the network threat protection section when I open up the console. This is a 64-bit version.

Hi Everyone,

For those who wish to install SEP 11 MR4 MP1a on Windows 7 RC here's what worked perfectly for me (of course after a couple of trial and error sessions ;-) ) 
 

1. Install LUSetup.exe to install Live Update  - DO NOT REBOOT -
   
2.  Open System Registry (regedit)
   go to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\services\SysPlant
    Change the value of the "Start" DWORD to 4  (Disabled) 
3. Reboot 
4. Install the **Unmanaged Client** (even if need it managed)  WITHOUT "Network Threat Protection" (so only Anti-Virus and Proactive Threat will be installed) 
5. Reboot
6. If you need to connect it to management Open SMC GUI go to "Help and Support" --> Troubleshoot  and import Sylink.xml from your managed package installation source..  (you can also use Sylink drop ..)
7. Update Policy and reboot
   
   Hope it works well for you guys as well .

Greetings,

I tried the new MR4 MP2 on Win7 32bit and it still crashes it.

I'm seriously hurting here guys.

When will we get Win7 support as it's now in a RC stage?
A lot of us are testing and developing on it and would love the piece of mind knowing we have some security coverage in the process.

Thank you and have a great day,

~Brett A. Scudder~

I have tested the new build on 64bit.  Everything seems okay except I am still getting that message the symantec is trying to communicate with windows security center in a format that is no longer supported.

Not sure this is symantec related but it is one of the few not MS apps loaded that could cause my issue.  If  I try to launch any of the MS games they crash after a few seconds of being open.   I am going to load up on another machine and try it with just Windows 7 loaded and then  install SEP and see what happens.

I am using SEP mr4mp2 with Antivirus and Antispyware only and it is running fine

I thought the latest MR4 was going to be good, it installed ok but then Security Center says that the firewall, malware aren't running and it is reporting in a format no longer accepted.  So, I'm back to avast.  I realize, well I don't realize cause I don't know all that there is in writing SEP to work with 7 while you're trying to keep it up to date and fix issues with other OS, but the thing is, while I'm testing it, I know I can't run SEP or I have to mess with too many other issues, ... so, while I'm testing Avast installs easy, works fine, I'm likely to be proned to just stay with Avast so I don't have to mess with anything in the future.

I'm hoping I'll have a chance to test SEP along with my testing setup of 7 and not extend the whole testingn thing farther - after the release.

 I've tried useing SEP on Win 7 beta and RC.

MR4, MR$ MP1a both caused bluescreen's after install with any option other than AV/AS installed.

I'm now running mr4mp2 on win7 rc with AV/AS and PTP.  Seems to be working well.  I find that odd as the notes didn't mention any PTP issues being fixed.  I did verifty that NTP causes the same bluescreen issue with mr4mp2.  Thank god for system restore.

Running MR3 (post some tweaking), MR4-MP1 amd MR4-MP2 on 3 distinct Win7 test boxes, and no issues till date except with MR4-MP1. It take a unsually long time to update adn then sometimes bugs out my running programs on the system.

Otherwise, I found Mr4-MP2 to eb pretty stable with no issues till now. (Been using Win7 ever since it was released to us Beta Testers and have gone round the block with SEP on it as well) :)

What seems to be the working combination to get a successful install of sep and appropriate install procedure?  I tried installing using the package and I got a blue screen but was able to bring it back online my bluescreen was from teefer.dll I think

Hi Paul,

The Windows 7 RTM (GA) date has been declared as 22nd October 2009.

It goes to all MSDN, Technet subscribers, a week or 2 weeks before the RTM date.

All API's would go to ISV's at least 3 months before the RTM / GA date, and build versions for OEM's go out to all partners around a month before to start building Windows 7 based systems for the market.

Any updates for us on when the new Windows 7 compatible build of SEP would be shipped / RTM'd?

October 22 is not RTM that is when it becomes available in stores and in wide availability.  RTM (Release To Manufacture) that is when it goes out to start  producing the DVD's, and OEMs get the code to start loading on to systems that can ship after the release date.    RTM will have to be sometime in late July for a release date of Oct 22.

I said RTM (GA) = General Availability > Then In stores (GA / Gold) = FPP (Full Packaged Product / Retail)

All OEM's will get the builds to use with WAIK / OEM Deployment kits in mid or late August.

Some info if it helps out - en.wikipedia.org/wiki/Software_release_life_cycle

We first deploy internally, then we have RTM, and we internally term the next release cycle as RTM (GA).