Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

A Better Push Deployment Wizard

Updated: 02 Jul 2010 | 12 comments
Bekir's picture
11 Agree
2 Disagree
+9 13 Votes
Login to vote

Hello,

I think it would be ver easy and nice to make push deployment wizard need much much less interaction.
It would be nice to be able to start the wizard, configure it, and leave it until it finishes.

These options would be great if existed:
- Stop trying to connect if there is no ping
- Adjust connection timeout value
- Auto-Skip non-responsive targets
- Auto-Skip targets which cannot be logged on
- Log skipped targets
- Save report to this directory : Browse...

I hope, these options come to life.
Regards,

Comments

Fatih Teke's picture
02
Jul
2010
1 Vote +1
Login to vote

I aggree

Hello Bekir,
I aggree your idea. It will be very helpful for us.

Best Regards.
Fatih

 Everything works better when everything works together.

mon_raralio's picture
05
Jul
2010
0 Votes 0
Login to vote

.

I like this idea.
Same goes for the Sylink tool. Seems to take forever at times.

“Your most unhappy customers are your greatest source of learning.”

Bekir's picture
06
Jul
2010
0 Votes 0
Login to vote

thanks guys :)

thanks guys :)

Best regards,
Bekir Burak Durmaz

Nourbakhsh's picture
08
Jul
2010
0 Votes 0
Login to vote

Better Error Log in Push Wizard

Dear Sir's, Thank's for your Good Idea, i think that there should be a Log file for showing the Problems accured during push deployment wizard .
As i know, there isn't any Log when Problem accure during Push Wizard & we will see a Common Error Windows says this Wizard Failed without any Log. !!!

Bekir's picture
10
Jul
2010
0 Votes 0
Login to vote

That's absolutely necessary

That's absolutely necessary as well Nourbakhsh.

I cant believe someone disagrees the idea by the way :) For what reason? :DD

Best regards,
Bekir Burak Durmaz

mon_raralio's picture
13
Jul
2010
1 Vote +1
Login to vote

Maybe we need to add a little

Maybe we need to add a little more weight with this idea. I'm just thinking that deployment only happens during installation of SEP for the first time. I'm not even using this for day to day searching of PCs without an AV installed on them - especially if the server has been up for quite some time. Maybe post some examples of how you'd use it. :D

“Your most unhappy customers are your greatest source of learning.”

Bekir's picture
13
Jul
2010
1 Vote +1
Login to vote

Hi, You're right, people

Hi,

You're right, people usually do not use it after the first deployment. But the tool itself is so dummy even if it is used only for once :)
I'm doing mass installations for many companies and I cannot even get a decent output about what happened with the installation.

If they'll ever going to improve the tool, I hope they at least consider or review this thread :D

Regards,

Best regards,
Bekir Burak Durmaz

Absoblogginlutely's picture
23
Jul
2010
0 Votes 0
Login to vote

A log file is critical to work out whether an installation has occurred or not.
I often get cases where pc's have not upgraded for some reason or other when deploying a new package. Discovering unmanaged computers does not find these older installation computers as they are actually managed - just an old version. Therefore the only way (that I'm aware of) is to deploy with the push wizard.

I have found that half the time you can't connect to the machines by browsing but adding the names in one at a time by hand is working.

It would be nice if the system would actually detect unmanaged computers and report but I've yet to have this happen.

Bekir's picture
07
Aug
2010
0 Votes 0
Login to vote

You can even add an option to "not to push to clients where any SEP is already installed"...

Best regards,
Bekir Burak Durmaz

shango's picture
12
Dec
2010
0 Votes 0
Login to vote

Any news about this

I am in the initial phase of deploying to about 800 servers and was looking for something a little more reliable that this sad excuse for a tool.

Bekir's picture
13
Dec
2010
0 Votes 0
Login to vote

Did you guys ever confronted

Did you guys ever confronted that the wizard just disappears just a little while after you start pushing the package?

It just vanishes, no signs of crashing, it just exits...

For this reason I am still using the ClientRemote.exe of MR4 MP2 :(

Best regards,
Bekir Burak Durmaz

mon_raralio's picture
13
Dec
2010
0 Votes 0
Login to vote

I have experienced this

I have experienced this during some deployments. As I recall, at least one of the clients doesn't allow remote sessions (RDP service) or have files sharing disabled or is not joined to the domain so our domain admin IDs does not work. When that happens, the deployment just quits whether the previous clients on the list are at the process of deploying or not.

“Your most unhappy customers are your greatest source of learning.”