I want to install my application into client PC (1000 PCs) without going and installing it manually.
For example, TrendMicro antivirus installs Antivirus client to every client PC remotely just sitting from the Admin PC.
I want same procedure like this.
Can you please help me in this?
Thanks
You could deploy the software from a network share using GPO (Group Policy) linked to an organizational unit (OU) in Active Directory, per machine.
And as #scheien suggest, by using Group Policy after building an MSI file. here is a link showing you how to do it
Related
I've written a c# application which is intended to be ran on multiple computers within a network. The problem im trying to figure out is how I can share some common files between all the computers within the network.
I was handling this before by installing the software on one computer, storing a path string as an application scope setting during install, and then creating exe shortcuts on all other computers in the network which point back to the original installs exe.
Application deployment to network drive
I read this link and they talked about how it would be better to use clickonce rather than using a network share. The network share was the only way I could think of to have a common files directory. Are there any other ways to accomplish this?
Part of the installation process should ask the user for the path where the shared files will go. As long as each user enters the same path your good. That's the trick...
One way to solve that is to provide a silent installer mode that can be run with a preset of values the installer will need. You can then push the installer via group policy to all of the machines in your network.
I'm not sure what installer tech you are using, but WIX will create MSI's that support silent installation.
I made a site using VS10 Ultimate [ASP.NET] and when I build & run it runs the severer locally, while I want to test it for security issues via Linux.
How can I run it globally ?
Thank you!
Your development machine probably has IIS installed. Copy the code or the compiled code to the web root of this installation. If you want to put it on another computer, then that will need to have IIS, relevant version of .Net installed.
It would also help if you can setup your local DNS to resolve the name for your computer within the LAN setup so that you can reache the machine using a name rather than the IP.
This will allow you to test the security issues that are client side. For Server side security issues, you will need to create a server in your LAN that is configured similar to the actual server where you would be hosting your site.
You need to set up the site in IIS Server installed in your Windows machine to run it locally
See the links to learn more:
http://www.beansoftware.com/ASP.NET-Tutorials/Set-Up-IIS-ASP.NET.aspx
http://support.microsoft.com/kb/323972
You need an ASP.NET hosting service.
I am working on VS 2010 with .net 4 (OS: Windows XP). I want my application to have update feature. I have only one computer. How can i deploy the application it to test the update feature?
Currently i am publishing my application in a folder in my documents
I tried publishing to local FTP using XAMPP but it was unable to check for updates on FTP.
Now i have installed IIS to make a local HTTP server to deploy my application there but it asks for Front Page Server Extension then was asking Front Page.
All i need is that my application can update it self. Original requirement was patch update but i don't know how to do that. I think using ClickOnce is enough.
Create a network share on your local machine and publish to that; when you install the application, make sure to install it via the network share too.
A server had to be re-built after Hard drive crash..
After installing exact Image of the Server software, The WMI fails to connect when called (RPC Server is unavailable) from another computer.
However, Can connect using Visual Studio (2005) Server Explorer.
The calling server is Windows 2000 server and the called is Windows 2003. Both computers firewalls are disabled and appropriate rights are assigned to the calling and called accounts.
Check both the server and the client's event logs for any suspicious entries that might suggest what is misconfigured. Also, check what are the identities of Visual Studio and the app that calls WMI and if they are not the same, what's the difference in their security configuration.
The culprit is simply the netbios name..
Prior to re-build the computer name was 'rulestream'
After re-built some how it is given 'rulestream.myDomain.com'
I was able to spot the difference using Sysinternals TcpView.. Thanks Sysinternals
Our company uses Citrix to remote into a terminal server for remote users to launch smart client apps within a virtual window on their machine.
The problem is that smartclient apps are being downloaded each time the user launches them eventhough the version on the remote citrix server has not change. This is due to the user's profile being purged each time they close their Citrix session.
Is there any way to avoid this and still continue to purge the user's profile? Not purging the profile leads to wasted space on the citrix servers and corrupt profile issues.
I can't speak to details on Citrix servers. However, with ClickOnce you have no say over where an application is installed. It's installed under the user profile, no ifs, ands, or buts. One of the major goals with ClickOnce was improved security and installing apps to the profile makes that easier. So, if you're clearing the profile, you're stuck.
However, couldn't you just deploy the app to the Citrix server without ClickOnce? Most .Net apps can just be xcopy deployed, so it seems it would be pretty easy to write a few batch files to copy the latest deployment to your Citrix server and skip ClickOnce all together.
The way to do this in the Citrix environment is to use the Citrix URL Content redirection feature (in Feature Release 2) to redirect the ClickOnce URL to the local machine (http://xxx.xxx/myapplication.application). This will cause the browser window to open on the local machine and not on the Citrix machine. Once this happens, ClickOnce takes over and installs on the local user's machine, instead of inside Citrix. Executing locally will still give you all the normal ClickOnce benefits.
You don't want to install inside Citrix due to the problems in codeConcussion's answer. Plus, ClickOnce doesn't support mandatory or temporary profiles, which is probably what the user has inside Citrix.