Wednesday, 5 June 2013
Ruckus ZoneDirector & Ruckus Zoneflex 7343
Wednesday, 22 May 2013
ESET - how to push install to client from ESET Remote Administrator (KB)
ESET Knowledgebase
How do I push install to client workstations using ESET Remote Administrator? (5.x)
KB Solution ID: SOLN2982|Last Revised: April 09, 2013http://kb.eset.com/esetkb/SOLN2982
In order to complete the setup of ESET Remote Administrator and protect your network with your ESET security product, you will need to perform a four-part process:
- Download and install ESET Remote Administrator and ESET endpoint products
- Set up your Mirror server
- Create an installation package (containing your ESET security product and a configuration .xml file)
- Push installation package out to client workstations
NOTE:
This article outlines parts three and four. For detailed instructions on parts one and two, see the following Knowledgebase article:
Important!
Before attempting a push installation, please complete all of the items in our ESET Remote Administrator Push Installation Requirements and Checklist.
VIDEO: How do I push install to client workstations using ESET Remote Administrator? (5.x)
III. Create an installation package
- Open the ESET Remote Administrator Console (ERAC) by clicking Start
All Programs
ESET
ESET Remote Administrator Console.
- Click the Remote Install tab, then click Actions
Manage Packages.
- Click Add in the Installation Packages Editor window.
Figure 1-1
- Click Download From The Web and select the ESET security product that you wish to push install. Make sure that the version number is current and that you have the correct package selected. This information is displayed in the MSI File Descriptionfield. Click Create.
Figure 1-2
Click Save As and give your installation package a descriptive name, then click Save. Click Close to return to the ERAC window. You are now ready to continue to Part II.
NOTE:
Before saving the package, you have the option to either make changes to the configuration associated with this installation package, or to select a pre-configured ESET Configuration File (.xml) that you would like to associate with this installation package:
- Edit the configuration: Click Edit, make your desired changes and click Console. Save the file (as outlined in step 5 above) and proceed to step 6.
- Select an ESET Configuration File (.xml): Click Select, navigate to the ESET Configuration File, select it and click Open. Save the file (as outlined in step 5 above) and proceed to step.
To perform a silent installation (optional), run the file from the command line using the following switches:
/quiet REBOOT="ReallySuppress" (see Figure 1-3)
For example: C:\Users\UserName\Desktop\ESET32.exe /quiet REBOOT="ReallySuppress"
To display a progress bar during the installation, run the file from the command line using the following switches
/qb! for progress bar with no cancel option.
For example: C:\Users\UsersName\Desktop\ESET32.exe /qb REBOOT="REallySuppress"
Figure 1-3
IV. Push installation package out to client workstations
Important!
Before attempting a push installation, please complete all of the items in our ESET Remote Administrator Push Installation Requirements and Checklist.
- In the main program window of the ESET Remote Administrator Console, click the Remote Install tab.
- Select the client workstation(s) that you wish to push an installation package out to, right-click, and select either Windows Push Installation or Linux/Mac Push Installation based on the type of push installation.
Figure 2-1
Click the image to view larger in a new window
- If any of your clients are password protected, select that client and click Set. Enter the client's logon credentials in the Logon Information window and click OK (see Figure 2-2).
NOTE:
If the logon information is the same for all the clients involved in this push installation, you can click Set All so that you only have to enter logon information once.
- Click Next.
Figure 2-2
- Select the appropriate installation packaged from the Type drop-down menu. In this example, we are pushing out to client workstations running Microsoft Windows, so we will select ESET Security Products package. Then, select the installation package you created earlier from the Name drop-down menu. Click Next.
Figure 2-3
- Verify the Task Settings in the final window, including the name of your Remote Install task and the specific time at which it will be performed. If necessary, make changes to the settings here. Click Finish to complete the push installation task.
Figure 2-4
NOTE:
To check the status of your push installation task, click the Install Tasks tab, then double-click the entry that represents your current task. In the Properties window, the status of your push installation will be visible next to State.
Tuesday, 21 May 2013
Google Chrome - delete history via batch file
Google Chrome
Chrome stores history, cookies, cache and bookmarks in various databases and directories in the per-user application data directory at C:\Users\<username>\AppData\Local\Google\Chrome\User Data. The easiest way to get rid of all this data is just to erase everything there. Chrome creates this directory anew if it finds it missing.
@echo off set ChromeDir=C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data del /q /s /f "%ChromeDir%" rd /s /q "%ChromeDir%"
IE Clear history by batch file
To use these commands, just run them from the command line, the start menu search box in vista, or a batch file.
Temporary Internet Files
RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 8
Cookies
RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 2
History
RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 1
Form Data
RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 16
Passwords
RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 32
Delete All
RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 255
Delete All – "Also delete files and settings stored by add-ons"
RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 4351
Monday, 29 April 2013
Friday, 26 April 2013
IPAD Roll-out program (at School)
Friday, 12 April 2013
Meet your new Best Friend "ADplus"
3. setup the symbol path ie:
I added the symbol path: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
4. Install winDBG