Tuesday, June 16, 2009
Installshield: Create installation response file
---------------------------
1. Run the command > C:\Temp\setup.exe -r -f1c:\Temp\setup.iss
Note: there should be no spaces in between -f1 and the directory path and its - not / that need to be there with the switches.
2. Once the setup.iss file is created try to run the installation with silent parameters this time it would definitely install. eg. setup.exe /s /f1 "c:\Temp\setup.iss
Sunday, May 31, 2009
Windows Server 2008: Enable ICMP (Ping) replies
Enable
netsh firewall set icmpsetting 8
Disable
netsh firewall set icmpsetting 8 disable
Monday, May 25, 2009
BlackBerry: Application deployment using BES
In the BlackBerry Enterprise Solution environment, perform the following actions to deploy a Java application using the BlackBerry Enterprise Server and Application Control policy rules.
Note: Allow four hours for application deployment on multiple BlackBerry devices.
------------------------------------------------------------------------------------
Action
Add the application files to a shared folder.
Procedure
The administrator or application developer completes these actions.
1. Create or obtain the .alx and .cod files for the application.
2. Create a uniquely named folder, maintaining the application’s file structure, in the network location that hosts your shared applications:
3. Copy the .alx, .cod, and .dll files to the unique folder.
------------------------------------------------------------------------------------
Action
Index the application.
Procedure
The Application Loader reads the list of installed software in the software index and uses the index to locate the applications to install.
1. At the command prompt, type cd
2. Type loader.exe /index. The Application Loader builds the software index structure and adds any missing index files.
Note: If you modify an .alx file after you create a software index, re-index the applications.
• At the command prompt, type cd
• Type loader.exe /reindex.
------------------------------------------------------------------------------------
Action
Share the application folder.
Procedure
Software configurations must be able to access the application through a Universal
Naming Convention (UNC) path to the shared network drive.
1. Navigate to the application’s folder.
2. Right-click the folder, and then click Properties.
3. Click the Sharing tab.
4. Select Share this folder. Provide read-only permissions.
5. Set any other required options, and then click OK.
------------------------------------------------------------------------------------
Action
Set an IT policy rule for the user account.
Procedure
This action is optional.
Notes: You must set the Disallow Third Party Application Downloads policy to False.
The following steps describe the procedure for setting an IT policy rule for the
BlackBerry Enterprise Server Version 4.0.4. If you have a BlackBerry Enterprise
Server Version 4.1, see the BlackBerry Enterprise Server System Administration
Monday, April 27, 2009
unknown error occurred (0xE800002E) when Syncing iPhone Applications
2. Delete app from Mac ~/Music/iTunes/Mobile Applications
3. "re-purchase" app (it'll say you already have, just continue and it'll download the latest version for free)
4. Sync iPhone and your fresh app will be there
Tuesday, April 21, 2009
"The call could not be completed because security levels do not match"
I had a weird issue with my OCS in the last 2 weeks, I will blog about the first one in a later post, the problem that I will talk about it here is that I couldn’t join a conf. or do any one to one conf. with any of my Tandberg video endpoints from OCS client.
- When you do a call from OCS client to Codian MCU the following error appears in the OCS client “The call could not be completed because security levels do not match".
- In the MCU ou will find the following error: Unable to provide video channel - possible bandwidth/codec issue
Cause:
Tuesday, April 14, 2009
ManageSoft package distribution job remains pending
When viewing the report summary for distributed packages, a package distribution job remains in a pending state and only the Package_Name_metapkg.ndc file has updated on the deployment location (DL).
Answer/Solution:
Firstly you will need to delete the pending jobs in the JobQueue on the remote DL.
- On the remote DL, check that the ManageSoft Connection Agent service is started.
- Browse to C:\Documents and Settings\All Users\Application Data\ManageSoft Corp\ManageSoft\Replication Agent\JobQueue
- Rename the directory JobQueue to Backup_JobQueue
- Browse to the package directory in the Distribution cache which is located in the Warehouse e.g. Z:\Data\Warehouse\Distribution\Cache\Common\Package_Vendor_PackageName_PackageName
- Rename the Package_Vendor_PackageName_PackageName to Backup_Package_Vendor_PackageName_PackageName
- Back on the ManageSoft administration server, kick off a new distribution job to the remote DL where the package failed to distribute.
- Once package distribution is successful, delete the Backup_ directories that you renamed.
If the above fails, log a call with your support provider.
Monday, April 13, 2009
Enable Offline Folders tab in Windows Explorer
To enable the tab:
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\NetCache]
"NoConfigCache"=dword:00000000
To disable the tab:
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\NetCache]
"NoConfigCache"=dword:00000001