MR2 installed, MR1 client installation packages won't delete

12

Apr

2008

0 Votes 0

Sandeep Cheema

Yeah, You are right Scott, It doesnt allow to delete the old package, even after deleting all the packages from the inetpub\clientpackages, It repopulates as soon as the service is restarted.

I am trying to see what could be done.

BTW, What all things are you trying to make that happen, maybe I would get a direction from that.

Thanks.

De facto when AV does something, it starts jumping up and down, waving its arms, and shouting "Hey! I found a virus! Look at me! I'm soooo goooood!"

13

Apr

2008

0 Votes 0

SKlassen

So far, I've only tried highlighting the package and clicking delete under tasks. Tomorrow I'll try to take a look in the db and see if I can find the flag that's locking the packages.

14

Apr

2008

0 Votes 0

SKlassen

Not seeing anything that really stands out in the DB.

Edit: Submitted case # 320-104-149 to Symantec Support

Message Edited by Scott Klassen on 04-14-2008 09:34 AM

14

Apr

2008

0 Votes 0

Screen_Name

I would like to know how to get these deleted as well. We are running on a low HD server so all the extra space counts.

Thanks,

SN

14

Apr

2008

0 Votes 0

Mike T

same issue here also ..

also, a small bug. When I went into Admin to add a new client package (not having any success at the other end), it gave me a nice warning screen that told me that "an existing package was already assigned to that group and was I sure that" ................ the rest ran off the page and I couldn't see it. So I took a deep breath and hit the button and off we went. But seriously, it could of been asking if I wanted to replace it or keep it.

14

Apr

2008

0 Votes 0

Knottyropes

MR3 should be around the corner then.:smileysurprised:

14

Apr

2008

0 Votes 0

SKlassen

The word back from the engineer assigned to my case is that he can't replicate the issue. Sent him more information.

14

Apr

2008

0 Votes 0

SKlassen

I should mention that anyone else experiencing this problem should also file a support case. The more cases that get logged, the quicker it will get fixed. Feel free to reference my support case above when filing yours so they can be linked together for tracking purposes.

15

Apr

2008

0 Votes 0

Hurricane Andrew

Same thing here. I made sure to remove the old install package from the groups to which they were assigned, but still as unable to delete them. Error message indicates that:

"SEP version 11.0.100.1375 for WIN32BIT" is the latest patch. You cannot delete it.

"Hurricane" Andrew

Milford, Delaware

15

Apr

2008

0 Votes 0

Moorbo

I'm also having the same exact issue - both client versions are listed and it won't let me delete the previous MR1 client packages.

15

Apr

2008

0 Votes 0

SKlassen

I'm really thinking that there's a locking "flag" somewhere in the db causing this behavior. I've dug around a little bit, but not found anything yet.

15

Apr

2008

0 Votes 0

Qfactor

I'm another one with the same issue. Cannot delete the MR1 package....

15

Apr

2008

0 Votes 0

jkupski

Same error on my side (I also have the "clients not updating" problem.)

I referenced the case that Scott posted (320-104-149) which will hopefully give support some more visibility into this issue. If anyone else is opening a case on this problem and wants to reference mine as well, my case number is 320-104-517.

15

Apr

2008

0 Votes 0

Bumiputera

Well,

When i try to upgrade all my client to MR1, i'm delete previous version of SEP before MR1. Then all my client can be upgraded to MR1 automaticly. Before that, in C:\Program Files\Symantec\Symantec Endpoint Protection\Download directory create *dax file but always failed to complete. Since i delete the previous version then in that directory create full.zip and succed in upgrade.

That's way i'm trying to delete the MR1 ... it's also to save my space to ..

15

Apr

2008

0 Votes 0

Lobster1071

Same exact issue here after installing MR2. Hard drive space very low on one of my servers, and trying to delete the 1000.1375 install packages. Keep getting the error "Symantec Endpoint Protection version 11.0.1000.1375 for WIN32BIT is the latest patch. You cannot delete it."

Hopefully this will have a solution soon.

15

Apr

2008

0 Votes 0

Avanza Solutions

same problem, cant delete the client install package created by version 11.0.1000.1375

will appreciate if someone can share a solution for this.

16

Apr

2008

0 Votes 0

Crashball

Same here. Can't delete the 11.0.1000.1375 package. Also having the issue with auto-upgrade not working.

Is there a log somewhere that i can be checking to see if anything is happening? I see nothing on the clients, i don't hink it is even trying to push it out.

Message Edited by Crashball on 04-16-2008 06:22 AM

16

Apr

2008

0 Votes 0

S3c123

Also can't delete the 1375 rev. however auto-upgrade is working. Oddly the issue I'm having is exporting a new package, seems to be including policies prior to MR2 upgrade. Then can't get the clients installed with the new agent to recieve a new policy (though communication appears fine ...little green dot)

16

Apr

2008

0 Votes 0

LE2Strat

Having the same issue, can't delete/remove the MR1 packages because SEPM thinks they are the latest release.

I would love to call in and report I also am having the issue so it gets fixed sooner, but since the last few times I have called Symantec my average hold time before speaking to somebody has been 50-75 min, I am going to pass in hopes they get a fix and it is posted here.

16

Apr

2008

0 Votes 0

Derek Davis

Ditto. Same here.

16

Apr

2008

0 Votes 0

Shaun Crandall

Same here.

16

Apr

2008

0 Votes 0

SKlassen

You can save the wait time with Symantec Support by registering at and using mysupport.symantec.com. It's a web interface for starting, tracking, and communicating about support cases. Much more convenient for non-emergency support issues.

17

Apr

2008

0 Votes 0

Aj Neo

Accredited

Client installation package will not delete - MR1 package - Only want MR package

Has anyone found a solution to this problem ? If so could you post it.

17

Apr

2008

0 Votes 0

Screen_Name

bump...

Waiting on symantec reply

17

Apr

2008

0 Votes 0

SKlassen

With my case, it's still an information gathering game. The engineer asks questions, I answer, rinse and repeat.

17

Apr

2008

0 Votes 0

jkupski

The engineer working my case has said "this seems to be a widespread problem, and I have successfully replicated it in my test environment" and he's in "information gathering" mode as well. He's supposed to contact me Monday with an update about what's going on (something I have no problem with, as this is an annoyance issue and not a critical bug.)

17

Apr

2008

0 Votes 0

Abhishek Pradhan

Hello,

I was working with Scott Klassen today on this issue, and woudl like to inform all that we at Symantec are currently working to rectify this glitch.

Cant post too many details here, but would like to request that all please bear with us on this.

Abhishek Pradhan, PMP, MCT
Consultant | Microsoft Corp.
Blog: http://blog.abhishekpradhan.net | SIG Lead - Pune IT Pro (Microsoft Pune User Group) | http://www.puneusergroup.org

17

Apr

2008

0 Votes 0

Hurricane Andrew

Thanks for the update! These forums are truly a credit to Symantec, and are greatly appreciated by those of us out in the field!

"Hurricane" Andrew

Milford, Delaware

17

Apr

2008

0 Votes 0

SKlassen

Yep, we laughed, cried, and experienced the whole gamut of human emotion.

Seriously though, we attempted a few different things, trying to find a quick and easy workaround for everyone. In the end it was looking like something for the programmers, so Abhishek is going to have it worked on.

Next time I come up for re-licensing, I'll demand the sales people take one third of it to add to Abhisheks' paycheck. The rest gets split between Sandeep and Paul. :) Somehow I don't think they'll go for it though.

18

Apr

2008

0 Votes 0

tilallr1

Also have the problem. Not a huge issue or anything. But glad symantec is looking into it.

21

Apr

2008

0 Votes 0

LE2Strat

bump

Has anybody from Symantec heard anything yet? What table are these listed in in the SQL DB? I am curios to see if I can force them to delete in my test enviroment.

21

Apr

2008

0 Votes 0

John T. Croson

You could always do a complete re-install of SEPM....I'm getting pretty good at it. :smileyvery-happy:

IT Manager
http://www.ihbsonline.com

22

Apr

2008

0 Votes 0

Joe T

Any word on a fix for this yet? I'm seeing the same issue. Thanks.

22

Apr

2008

0 Votes 0

Abhishek Pradhan

Well, still working towards it.....awaiting word on this from the devp. team.....please bear with us.....we be bearing with this to.....:smileyhappy:

Abhishek Pradhan, PMP, MCT
Consultant | Microsoft Corp.
Blog: http://blog.abhishekpradhan.net | SIG Lead - Pune IT Pro (Microsoft Pune User Group) | http://www.puneusergroup.org

23

Apr

2008

0 Votes 0

DW1 IT Department

Hello!

Did the update today --> same problem!

greets

24

Apr

2008

0 Votes 0

Screen_Name

bump for reply

25

Apr

2008

0 Votes 0

diverdaveman

I finally got mine to work (MR1 package to delete). Here is what I did.

Login to the console
Go to Admin, then Install Packages
Click on 'Upgrade Groups with Packages' and walk through the wizard
When the wizard finishes, go back to Clients, then Install Packages

You should now see at least two packages: one MR1 package and one MR2 package. Now delete the MR1 package.

I hope this works for others. This was very aggravating for us as well. Maybe the moon was just for me or something.

Dave

25

Apr

2008

0 Votes 0

Clint

At least for me, deleting the MR1 packages from the client groups isn't the problem. Actually deleting them from Admin->Install Packages is. Certainly it's not a show stopper but would be nice to clear the space used by MR1 from my server.

Clint

25

Apr

2008

0 Votes 0

Sandeep Cheema

diverdaveman,

That didnt work for me.

I think there's some confusion here, It's about the "client packages" under "admin > Install packages" rather than "clients > install packages"

Symantec's woorking on it though, Now don't lash at me..........L:smileyhappy:L

De facto when AV does something, it starts jumping up and down, waving its arms, and shouting "Hey! I found a virus! Look at me! I'm soooo goooood!"

29

Apr

2008

0 Votes 0

LE2Strat

BUMP BUMP BUMP.....any word yet?

Where are these listed at in the database? Can't you just stop the service and use a SQL command to delete them from the DB?

29

Apr

2008

0 Votes 0

Helios67

I am just now in the review process for upgrading to Endpoint Protection. I have looked at number of reviews and comments and then came here to see so many people asking how to 'Uninstall' the product. Can I get an honest appraisal from Symantec on whether I should hold off on this until some of the bugs have been worked out? I run an IT department for a medium size company (appx. 200 hosts) and can not afford to have a lot of problems.

Also, I noticed the post about not posting the CleanWipe tool for general download due to the possibility of a hacker getting it. Hacking is now a professional enterprise with Billions in annual profits world-wide. How many hacking groups do you think have fully licensed copies of Symantec AV (Enterprise, Corporate, etc), not to mention McAfee, Blink, AVG, etc. etc. ? They want it...they got it. I don't know if there is a better way to control it or verify customers, but just requiring someone to open a ticket won't keep it secure. I realize you know this though and I don't mean to patronize at all.

Anyway. Just nervous about installing this product now that I've read a lot of reviews. I want to because it will let me consolidate some software and enable me to control things such as USB devices, but...

Thank you in advance for your reply. :smileyhappy:

05

May

2008

0 Votes 0

Screen_Name

Is there a resolution to this problem? I still can't find a KB.

Thanks,

06

May

2008

0 Votes 0

Knottyropes

I am like so afraid to install MR2. But I dont want to uninstall and reinstall just to rid this extra stuff.

06

May

2008

0 Votes 0

Abhishek Pradhan

Hi Screenname, there is a KB, but unfortunately its Internal only.

Abhishek Pradhan, PMP, MCT
Consultant | Microsoft Corp.
Blog: http://blog.abhishekpradhan.net | SIG Lead - Pune IT Pro (Microsoft Pune User Group) | http://www.puneusergroup.org

06

May

2008

0 Votes 0

burningtower

Well, Isn't that special, and so very helpful too!

06

May

2008

0 Votes 0

LE2Strat

Yeah, I agree. But most companies, including Symantec, wouldn't publish a KB article for public view that basically read "Our product has this particular problem and as of this time we have no clue how to fix it."

I am sure the KB will be made public once there is a solution.

For the most part, MR2 is great so far. No problems on my side with the exception of this bug, and it isn't a show stopper, just an annoyence, but I understand it could be a problem for people who are tight on disk space though.

Message Edited by LE2Strat on 05-06-2008 11:06 AM

06

May

2008

0 Votes 0

Greg Huntzinger

I finally have MR1 working (with the exception of one client) and I'm worried about installing MR2 and going back to spending all day on the phone with support. Since most of the folks in this (very long) thread have installed MR2, would you do it again or wait?

Thanks!

06

May

2008

0 Votes 0

LE2Strat

MR2 is WELL worth the upgrade since it fixes the disk space issues on the client with the VirusDefs folder and the embedded database size (if you are using that, I use SQL). Going from the initial release to MR1 pretty much gave me the idea on how an upgrade goes, so going to MR2 was easy.

Message Edited by LE2Strat on 05-06-2008 12:20 PM

06

May

2008

0 Votes 0

Lobster1071

Yes, I agree, MR2 did seem to help a lot with the space issue. The program no longer eats up 2GB+ of valuable C drive space for me.

Plus the MP1 upgrade was a dress rehersal for doing the MR2 upgrade, and it really went much more smoothly.

To be very honest though, I do think these last installations that I've done with Endpoint (to 4 different servers) will be my last time using a Symantec product for network security. Simply too many bugs, too much of a resourse hog, too much of a configuration nightmare, and incomprehensible wait times when you need support. These forums were the only shining light in resolving the various issues that I encountered.

Looking into other product options after these licenses expire.

07

May

2008

0 Votes 0

Screen_Name

Abhishek PradhanDo you know a time frame when they will publish the KB or when this problem will be resolved/patched?

Thanks,
SN

07

May

2008

0 Votes 0

Abhishek Pradhan

@ Screen Name

I really wish I had some idea about the time frame. Best guess is that this would be fixed in the MP-1 for MR-2

Abhishek Pradhan, PMP, MCT
Consultant | Microsoft Corp.
Blog: http://blog.abhishekpradhan.net | SIG Lead - Pune IT Pro (Microsoft Pune User Group) | http://www.puneusergroup.org

07

May

2008

0 Votes 0

Knottyropes

So....when is MR1-MP1 sheduled?

07

May

2008

0 Votes 0

Abhishek Pradhan

MR2-MP-1 is scheduled for sometime in May, Dont know exactly when. Will keep you posted as and when we get an update on this.

Abhishek Pradhan, PMP, MCT
Consultant | Microsoft Corp.
Blog: http://blog.abhishekpradhan.net | SIG Lead - Pune IT Pro (Microsoft Pune User Group) | http://www.puneusergroup.org

08

May

2008

0 Votes 0

Screen_Name

Thanks Abhishek for keeping us up to date.

15

May

2008

0 Votes 0

jkupski

BTT.

I haven't heard anything on my case for a couple of weeks (since "we've identified this is a problem and will probably be addressing it in a patch to MR2") and was wondering if anyone had a general update?

15

May

2008

0 Votes 0

Knottyropes

Maybe we can all roast marshmallows on our CPU's while we wait.

Maybe MR3 will come out next quarter.

Maybe it will be fixed.

Maybe.

15

May

2008

0 Votes 0

Faraz Zobairi

Symantec Employee

Hello Everyone,

Not getting this document published to the web was an oversight. Our policy is to publish a placeholder document for all known issues. As information regarding the issue evolves (i.e., workarounds discovered or fixes released), the document is updated.

Information on this issue:

"After migrating Symantec Endpoint Protection Manager (SEPM) to Maintenance Release (MR) 2, you are unable to remove the install package for MR 1"

http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008041711232948

Please note, this document was just posted, so it may take an hour or so for it to replicate to all of our web servers.

Regards,

Faraz Zobairi

Associate Manager, Symantec

Advanced and Backline Support

29

May

2008

0 Votes 0

BlackFog

Just want to queue here. I read the whole thread and awaiting a solution...

29

May

2008

0 Votes 0

jkupski

> MR2-MP-1 is scheduled for sometime in May

I'm guessing the schedule slipped? :)

Any updates on when we can expect to see MP1?

29

May

2008

0 Votes 0

Knottyropes

Just roast some marshmallows on your CPU and enjoy the good taste.

::burp::

Maybe we can get it by end of summer.

29

May

2008

0 Votes 0

Paul Murgatroyd

Symantec Employee

Accredited

Certified

at the risk of getting my head chopped off, English MR2 MP1 is due to be released internally tomorrow (30th) PST time, it should be available externally within a couple of business days after that.

Paul Murgatroyd
Principal Product Manager, Symantec Endpoint Protection
Endpoint twitter feed: http://twitter.com/symc_endpoint

03

Jun

2008

0 Votes 0

Anderson74

hi!

I want to now if there is a mr2 mp1 release for sepm?

I've found mr2 mp1 release for clients.

Thank you!

04

Jun

2008

0 Votes 0

Knottyropes

Not yet. hopefully soon.

04

Jun

2008

0 Votes 0

Abhishek Pradhan

Thanks to Scott, for giving me a starting point for this issue.

I've been working on some simple modifications to the SEPM installation, and I'll possibley have positive results in a few days. I'm trying to delete the multiple packages listed in the SEPM< and have had a fair amount of success, but wish to test this in a test production environment, before I type them here.

Gimme a few days, and I guess everyone might turn out happy with the results.Though the process is a bit tedious, it'll be worth the wait. :smileyhappy:

Abhishek Pradhan, PMP, MCT
Consultant | Microsoft Corp.
Blog: http://blog.abhishekpradhan.net | SIG Lead - Pune IT Pro (Microsoft Pune User Group) | http://www.puneusergroup.org

09

Jun

2008

0 Votes 0

SKlassen

Just to keep everyone informed of the progress on this issue.

Abhishek gave me his tentative fix for this issue over the weekend. This morning, I upgraded my production SEPM install to MR2 MP1 and found that afterwards the MR2 client install packages are not deletable, just like the MR1 packages. First I backed up my SEPM database, then implemented his fix to remove both the MR1 and MR2 packages from the database and I also removed them from the file system. So far, so good. They have not recreated themselves, nor caused any issues to this point. I've forwarded the information I gathered back to Abhishek for final testing, so he should be able to post instructions back here soon if he finds no further problems.

As a disclaimer, the fix is a workaround involving manual manipulation of the information in the SEPM database, which is not officially supported. Implementation of the fix would fall outside the realm of official support and is most likely done at your own risk, but Abhishek will be able to explain this in a more authoritative manner than I.

13

Jun

2008

0 Votes 0

Knottyropes

I just reread the top post.

So if I have SEPM MR2 and it has the MR1 packages

If I install SEPM MR2 MP1 the MR1 and MR2 packages will still be there unremovable?

This might explain why it is not realeased yet.

Message Edited by Knottyropes on 06-13-2008 02:41 PM

Message Edited by Knottyropes on 06-13-2008 02:41 PM

13

Jun

2008

0 Votes 0

Abhishek Pradhan

:smileytongue:Funny part is, it seems that only the MR2 packages are affected a lot. The MR 1 and MR2 MP1 packages are very stable.

DISCLAIMER - This fix is a workaround involving manual manipulation of the information in the SEPM database, which is not officially supported. Implementation of the fix falls outside the realm of official support and is done at your own risk.

If you are using SQL Server 2000, open the SQL Enterprise Manager, expand the SEM5 <or whatever name you may have given> Database, Right Click on the Tables Option, click on All Tasks, Run SQL Query.

If using SQL Server 2005, open the SQL Server Management Studio, select the Symantec DB and Rt. click on it and click on Tasks > New SQL Query

If using the Embedded Database, navigate to the following location -

<Drive Name>:\Program Files\Symantec\Symantec Endpoint Protection Manager\ASA\win32\ and execute the file dbisqlc.exe ; when prompted for the username and password, type in username as "DBA" minus the quotes, and the password would be the SEPM Admin login password (The FIRST password that you gave for the Admin account when you initially installed the SEPM)

Now run the following queries - <NOTE - The solution provided here is without any liabilities whatsoever. DO take a backup of your DB before you perform these steps, since improper execution of these steps WILL result in a corrupt and unusable Database !!!!!>

For deleting the MR-2 based packages (First query is for the 32 bit package, and the 2nd query is for the 64 bit package)

DELETE FROM BINARY_FILE WHERE ID = '9ED2C8307E2AAE03A8D7EC5E1D9B147B'

DELETE FROM BINARY_FILE WHERE ID = '5785CBBBBB970536B0D12487775BADD0'

Parse these queries individually for the to be effective.

For the RTM build based packages -

DELETE FROM BINARY_FILE WHERE ID = '46E5EE90B46959661066BFD13985AD8B'

DELETE FROM BINARY_FILE WHERE ID = 'E7966D168E15DEF85C2BF26D2BED8D43'

Once these commands are parsed successfully, you'll get message saying "1 rows affected....."

Exit the SQL / Embedded DB SQL prompts, log off from the SEPM, restart the SEPM Service, and then log back into the SEPM. You'll see that the relevent package has been deleted.

This same method can be applied in case you have migrated from MR-1 to MR2, or performed replication of the client install packages between sites, and when you try to export the MR2 based packages, all you get is a blank error pop-up with just the OK button. The solution here would be to delete the packages facing the error (from the DB), and then add them manually, BUT DO NOT GIVE THEN THE SAME NAME AS WAS THERE BEFORE. Name them SEP-MR2 32 bit, and SEP MR-2 64 bit when you add the packages manually, since giving the old names would render the package deletion process useless, as it would still have the same linker ID.

Hope this helps a lot of ppl.

Thanks a lot to Scott for performing a live run of the same, and confirming our tests :smileytongue:

Message Edited by Abhishek Pradhan on 06-14-2008 11:39 AM

Abhishek Pradhan, PMP, MCT
Consultant | Microsoft Corp.
Blog: http://blog.abhishekpradhan.net | SIG Lead - Pune IT Pro (Microsoft Pune User Group) | http://www.puneusergroup.org

15

Jun

2008

0 Votes 0

Abhishek Pradhan

bump - to keep it at the top for all to utilize.

Abhishek Pradhan, PMP, MCT
Consultant | Microsoft Corp.
Blog: http://blog.abhishekpradhan.net | SIG Lead - Pune IT Pro (Microsoft Pune User Group) | http://www.puneusergroup.org

16

Jun

2008

0 Votes 0

jkupski

Abishek,

Any chance of getting http://service1.symantec.com/SUPPORT/ent-security.... updated to reflect the information above?

16

Jun

2008

0 Votes 0

LE2Strat

OK, question then if this is officially not supported. When will a supported fix be available? I am guessing it will be addressed in MR3?

Looking at the fix you are deleting the packages from within the database. On previous upgrades it left the older install packages there for you to delete yourself.

Can we assume that MR3 will delete all install packages older than the ones distributed with MR3?

16

Jun

2008

0 Votes 0

Knottyropes

I bet they will make it users deleteable in MR3.

Would not be good idea to delete all older ones if you are still using the old ones before upgrading all the clients.

16

Jun

2008

0 Votes 0

Abhishek Pradhan

About the KB, I have no idea currently. Will check and let you know.

Most probably I guess too that MR-3 would fix this.

Till then, if you do need to remove the old packages, you can follow the steps outlined.

Abhishek Pradhan, PMP, MCT
Consultant | Microsoft Corp.
Blog: http://blog.abhishekpradhan.net | SIG Lead - Pune IT Pro (Microsoft Pune User Group) | http://www.puneusergroup.org

16

Jun

2008

0 Votes 0

jkupski

Does anyone know how to determine which rows in the database map to which install packages? I gather from Abishek's note above that it should be pretty easy to figure out, but the identifiers in the clientpackagess directory do not match up with the ones in the BINARY_FILE table.

Specifically, I'm trying to find the 32bit and 64bit package IDs for 11.0.1000.1375. Anyone have any ideas?

16

Jun

2008

0 Votes 0

Abhishek Pradhan

Beat you to it :smileytongue:. Am already looking for those linkers.....will post as soon as I find them.

Abhishek Pradhan, PMP, MCT
Consultant | Microsoft Corp.
Blog: http://blog.abhishekpradhan.net | SIG Lead - Pune IT Pro (Microsoft Pune User Group) | http://www.puneusergroup.org

18

Jun

2008

0 Votes 0

jkupski

Abishek,

Any update?

19

Jun

2008

0 Votes 0

Knottyropes

It all takes time.

But now that I have MR2 MP1 my MR1 will not delete.

Oh well, lucky me I have disk space.

20

Jun

2008

0 Votes 0

BlackFog

Same here, now I have three installation sets...

20

Jun

2008

0 Votes 0

Stormonts

Same problem for us.

23

Jun

2008

0 Votes 0

Abhishek Pradhan

@ jkupski,

2 more days. I'll have the IDs.

@ Blackfrog and Stormonts -

If you do wish to remove the packages, you can follow the previously mentioned steps (sql queries) to remove them.

Abhishek Pradhan, PMP, MCT
Consultant | Microsoft Corp.
Blog: http://blog.abhishekpradhan.net | SIG Lead - Pune IT Pro (Microsoft Pune User Group) | http://www.puneusergroup.org

23

Jun

2008

0 Votes 0

Stormonts

The IDs below are for 11.0.1000.1375 correct? We also have 11.0.2000.1567 and 11.0.2010.25 and I don't want to delete those.

DELETE FROM BINARY_FILE WHERE ID = '9ED2C8307E2AAE03A8D7EC5E1D9B147B'

DELETE FROM BINARY_FILE WHERE ID = '5785CBBBBB970536B0D12487775BADD0'

23

Jun

2008

0 Votes 0

Abhishek Pradhan

OH NO - :smileysurprised:

These are for MR2.....I'm looking for the ID's for the MR1 packages.....

Abhishek Pradhan, PMP, MCT
Consultant | Microsoft Corp.
Blog: http://blog.abhishekpradhan.net | SIG Lead - Pune IT Pro (Microsoft Pune User Group) | http://www.puneusergroup.org

23

Jun

2008

0 Votes 0

Abhishek Pradhan

I'll post the MR1 ID's here in a day or so - (Provided I find them in time..... :smileytongue:)

Abhishek Pradhan, PMP, MCT
Consultant | Microsoft Corp.
Blog: http://blog.abhishekpradhan.net | SIG Lead - Pune IT Pro (Microsoft Pune User Group) | http://www.puneusergroup.org

23

Jun

2008

0 Votes 0

Amol S (Jainam Technologies)

Dear Abhishek,

I am using SQL 2005 with Service Pack 2, I have replication Servers, After Run this query in My SQL 2005 run succeessfully. But I have run same as per you maintion in message. SEPM with Embadded Server I am getting error please find the link & Reply me.

http://www.2shared.com/file/3488218/6011699f/packages_deleted_from_sepm.html

Thanks,

Amol Sahare,

Jainam Technologies

23

Jun

2008

0 Votes 0

Abhishek Pradhan

Hi Amol,

For your query for the embedded DB, please open a case with support. They'll be able to help you with this the best. Secondly, you'll also see first hand how these things should be done to avoid crashing your existing AV Infra.

Message Edited by Abhishek Pradhan on 06-24-2008 01:16 PM

Abhishek Pradhan, PMP, MCT
Consultant | Microsoft Corp.
Blog: http://blog.abhishekpradhan.net | SIG Lead - Pune IT Pro (Microsoft Pune User Group) | http://www.puneusergroup.org

07

Jul

2008

0 Votes 0

Raptor01

Any updates on the MR1 package IDs?

08

Jul

2008

0 Votes 0

Bumiputera

Since the mr2-mp1 has been release out ? Is there any improvment for these case ?

09

Jul

2008

0 Votes 0

jkupski

Abishek,

Any update on the package ID issue?

09

Jul

2008

0 Votes 0

Wayne Wallace

I have installed the SEP 11.0.2010.25 version and still cannot get the previous client installed packages to remove: remaining client install packages 11.0.10000.1375 and 11.0.20000.1567 Any update and/or solution from Symantec would be nice.:smileysad:

18

Jul

2008

0 Votes 0

OB

48A8905E78A52F44645F356D44B31D29

and

239A2578D772B2D65DD31DFD7EBCA4D8

this is for 32 and 64 bit versions of 11.0.10000.1375

Message Edited by OB on 07-18-2008 09:25 AM

18

Jul

2008

0 Votes 0

OB

just run:

select *
from binary_file
where TYPE = 'ClientPackageFile'

and delete the IDs with the older timestamps.

MR2 installed, MR1 client installation packages won't delete

Comments

Links

MR2 installed, MR1 client installation packages won't delete

Comments

Would you like to reply?

Links

Technical Support

Symantec.com

Store

Community Stats