Deployment Tool
Sharyl Viken
I am having a problem trying to get the Office Deployment Tool ( www.microsoft.com/.../details.aspx ) to download Office images/software from Microsoft. When running the tool I was seeing lots of "Invalid TCP RST" entries all from my computer to a Microsoft server:
I then chose a different computer selection method (hostname and IP instead of AD) and used PSExec as the deployment method instead of the Built-In one; it once again gave me a "Success" status but nothing happened.
Has anyone experienced this before? My Google-fu failed me.
Additionally, I'm all ears if there's a different remote deployment method you can suggest. I found an .msi installation I could use, but when I listed it's command line switches, there was no flag for a license.
Probably not related, but why would you copy downloaded EXE installer to network share? Remote deployment tool is capaple of copying installer to target machine, so it just has to be accessible for Remote deployment tool when initiating deployment process.
Regarding deployment failure itself, would it be possible to test to run live installer manually on selected device, to verify that it works correctly when executed locally/manually? Is there actually any ESET product already installed on target machines? Or when you mentioned that "nothing happened", you mean that no ESET product was installed on target machine, or that you do not see new device in console?
The only reason I copied it on the network share was because I was not 100% certain if RDT is able to copy it or not and I was just testing the software before the company-wide rollout.
Absolutely nothing happened. The tool gave me a Success status but nothing was happening on the client computer itself, including no devices on the ECA page.
I ended up just figuring it out and it was an error on my end. I trusted the tool when it told me it was successful and didn't think about running Wireshasrk to see what was going on.
So after running Wireshark today I noticed that I was getting some HTTP errors thrown around when the tool was trying to download the executable (agent and the software itself) on the client machine. Upon further inspection, it was a firewall rule on the Sophos appliance that was causing the errors.
Lesson learned I guess, never rely 100% on automation tools and always do your own manual troubleshooting first.
My apologies for the inconvenience
The only reason I copied it on the network share was because I was not 100% certain if RDT is able to copy it or not and I was just testing the software before the company-wide rollout.
Absolutely nothing happened. The tool gave me a Success status but nothing was happening on the client computer itself, including no devices on the ECA page.
I ended up just figuring it out and it was an error on my end. I trusted the tool when it told me it was successful and didn't think about running Wireshasrk to see what was going on.
So after running Wireshark today I noticed that I was getting some HTTP errors thrown around when the tool was trying to download the executable (agent and the software itself) on the client machine. Upon further inspection, it was a firewall rule on the Sophos appliance that was causing the errors.
Lesson learned I guess, never rely 100% on automation tools and always do your own manual troubleshooting first.
My apologies for the inconvenience
The Discovery and Deployment tool assists you with adding endpoints to your Nebula or OneView environments. It scans your network and identifies devices suitable for agent deployment. The tool identifies endpoints where the Endpoint Agent is already installed. Custom criteria are used to discover endpoints and provide a snapshot of your devices before deployment.
No licenses, no invoices, no maintenance fees. The Vaddio Deployment tool is for our valued integration partners and AV managers who rely on Vaddio products to keep their AV installations running smoothly.
The Vaddio Deployment Tool requires authentication from each connected device and is an installed application. The application does not collect or transmit audio, video, or shared content, so meeting and business data remains private and secure. You can download firmware and install new equipment on sites without needing internet access. Vaddio does not harvest any data or benefit from giving away this tool other than making your experience better.
I am trying to setup publishing/deployment of an asp.net mvc project from visual studio to a box running IIS 7.5/Windows Server 2008. I found this useful tutorial and know I need to install something called web deploy.
Web Deploy is just a tool to help automate deploying your ASP.NET web site to many different web server configurations. It does not matter what version of VS you have. The latest version is 3.5 and it just several added features compared to 2.1
df19127ead