when you get the message, you neeed to check the path its referring to , it might be a folder or a file
make a note of that file and give full access to that.
run the uninstall again it should work fine.

your replication part is correct, install sepm, then add them to the existing one.i.e.. partners

How to add "Replication Partners" and Schedule Replication
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008052214120248

Hi Rafeeq,
Exactly this I've done before - but the domain admin full access was not enough :) So after adding me as admin it seems to be uninstalled finally. :)

Ok, and could you be so kind and advise me the link( or whatever ) reffering to the solution of my issue in second paragraph above. Thanks a lot..

Hello,

Best pratice for SEP replication:
http://service1.symantec.com/SUPPORT/ent-security....
Please come back and let us know, the result and more assistance or questions.

Best regards,
Frank

when working with replications you need to install each sepm as individual.
1 sepm - clients to that sepm
after that you install second sepm
replication between these two, the link what i sent you should explain it, please let me know if its confusing

Thanks guys..
I have one more question before start the replication. After reading the article you sent me, I want to ask if there is any way how to replicate clients only between the main server and another one, not between all the servers around(I mentioned I have about 30 servers that I want to replicate). I think like this: replication between Server1(DB1) and Server2(DB2) will create one database(DB12) that contains clients from both of them.. Databases DB1 and DB2 no longer exists. 
Is it possible create replications only like this:
Server1-Server2 (DB12)
Server1-Server3 (DB13)
Server1-Server4 (DB14)?
Because from that article I've read, its clear that I'm able to do only this replication:
Server1-Server2 (DB12)
Server12(DB12)-Server3 -->(DB123)
Server123(DB123)-Server4 -->(DB1234). Am I right?
I mean, that can be quite usefull, the final database on 30 replicated servers will be cca 30-times bigger than DB1. And this db will be on each of that servers.. Is this going to work fine?  
 

the sort of replication we can have here is called DAISY CHAIN
replications are just incremental..not the entire content.so its small
rep1-rep2-rep3-rep4 its like a chain replication.

In SEPM replication ,if you replicate 30 servers,all servers will have the data of all 30 servers .i,e.In each replication the additional site SEPM will download the full incremental data of first server(not only the data belongs to that server) and vice versa.In SEPM replication master SEPM to Additional SEPM is only possible.

Is it really required 30 servers if not reduce it,because the more no. of replicated server=more complication...You can check the possibility of GUP...

Ok guys, I see..
Is there perhaps another way to manage clients on remote servers(SEPM installed, clients deployed) from master server? Or this replication like we spoke about so far is the only option..
Unfortunatelly, now I have 15 servers, in near future is this count going to raise to 30. No way to reduce it.. :((

The DB is same, its shared ( replicated between) each server
You are actually managing all the servers from one sepm.
change made in one server is replicated to other server.
you can install the remote console.
while logging in put the server IP / name in the log in tab, to log in to that particular server remotely

Yes sure, I can do the same thing through remote desktop access..

I've made now one attempt with interesting result:
I added an anditional site(Server2-S2) from my primary server(S1). After replication, in console, the folder with managed clients(S1) has been replaced with the folder(clients managed on S2) from S2. S1 clients disappeared. On another site, S2 is managing the same clients like before-nothing changed, nor clients from S1 has been added here. I thought that after replication I'll be able to see clients in both consoles in both sites.. What went wrong??