The installation of PGP Desktop has not been initialized or the initialization settings have been deleted or damaged

This installation of PGP has not been initialized...

Article:TECH149607

|

Created: 2009-10-28

|

Updated: 2011-02-06

|

Article URL http://www.symantec.com/docs/TECH149607

Article Type
Technical Solution

Product(s)

Show all

Languages

Show all

Issue

When attempting to open PGP Desktop in a PGP Universal Server managed environment, you receive the following error message and PGP Desktop fails to open:

This installation of PGP has not been initialized or the initialization settings have been deleted or damaged.

Solution

This error can occur when the PGP preference files on the computer have become corrupted on PGP Desktop clients. To resolve this issue, stop the PGP Services and delete the PGP preference files. When PGP Desktop is restarted, the preference files will be automatically re-created.

Use the following steps to delete the PGP preference files:

1. Stop the PGP services by clicking the PGP Tray icon in the Windows system tray and then click Exit PGP Services.
2. Browse to the following folder for your operating system:
   
   Windows XP - C:\Documents and Settings\%user name%\Application Data\PGP Corporation\PGP
   
   Windows Vista - C:\Users\%user name%\AppData\Roaming\PGP Corporation\PGP
   
   Windows 7 - C:\Users\%user name%\AppData\Roaming\PGP Corporation\PGP
   
   

   Note: If the Application Data/AppData folders are hidden, you must change the folder options for Windows Explorer to show hidden files and folders. In Windows Explorer, click Tools > Folder Options then click the View tab. In the Advanced Settings window, click Show hidden files, folders, and drives then click OK.

3. Delete the PGPprefs and PGPpolicy files.
4. Click Start > All Programs > Startup and then select PGPtray.exe
5. If prompted, enter your license information and authorize the PGP Desktop software.

How to use Outlook policy to control credential prompts when connecting to an Exchange Server mailbox

1. Click Start, click Run, type regedit, and then click OK.
2. In the Registry Editor, locate the following key for Outlook 2013:
   
   HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\xx.0\Outlook\Security
   
   Where xx.0 is 15.0 for Outlook 2013, 14.0 for Outlook 2010, 12.0 for Outlook 2007, and 11.0 for Outlook 2003
3. Point to New, and then click DWORD Value.
4. Type PromptForCredentials as the name of the new registry entry, and then press ENTER.
5. In the right pane, right-click PromptForCredentials, and then click Modify.
6. In the Edit DWORD Value dialog box, and then type one of the following values in the Value data dialog box:
   
   

   Value	Description
   0	Cached credentials are used.
   1	Cached credentials cannot be used. You are always prompted for logon credentials.

7. Click OK.

 

Resolving "The User Profile Service failed the logon. User profile cannot be loaded."

Appears while attempting to logon in Windows Vista, 2008, 2008 R2 and 7.
Exact cause is unknown, but this issue may occur if the user profile was manually deleted by using the command prompt or Windows Explorer by a user or by some program. A profile that is manually deleted does not remove the security identifier (SID) from the user profile list in the registry. Since the SID is still present, Windows will still try to load the profile by using the ProfileImagePath that points to a nonexistent path. Therefore, the profile cannot be loaded.
This can also be a issue with the user profile entering into a backup state, or if the C:\Users\(User Name) user profile folder is manually renamed.

	1. Log on to the Computer Log on to the computer using the Administrator (or an Administrator-level) account. If the computer is not joined to a domain, reboot it and start your computer in safe mode, then log on using the Administrator (or an Administrator-level) account.
	2. Trawl through the Registry Open the Start menu. In the Start Search area, type regedit and press Enter (if prompted by UAC, click Continue/Yes). In regedit, go to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList Expand the ProfileList key and look for the SID key (named "S-1-5"...) with a long number that ends in ".bak". Click it, and look at the ProfileImagePath value in the right pane to verify that this is the user account profile that has the error. a) If you have two SID keys with the same number (with one ending in ".bak" and one showing the affected user account in the ProfileImagePath value), continue to Step 3; b) If you have just one SID key with the ProfileImagePath value showing the affected user account, proceed to Step 4.
	3. Two SID keys with the same number a) Of the two SID keys that corresponds to the affected user account, right-click the SID key that does NOT end in ".bak" and click Rename. b) Add .bk to the end of the numbers and press Enter. c) Right-click the other SID key that DOES end in ".bak" and click Rename. d) Remove only .bak from the end of the numbers (so that it has the same name as the other SID key did before you renamed it) and press Enter. e) Now go back and Rename the first one with .bk to .bak now at the end of the numbers and press Enter. Proceed to Step 5...
	4. Only one SID key ending in ".bak" a) Right-click the SID key that corresponds to the affected user account and click Rename. b) Remove only .bak from the end of the numbers, and press Enter. c) In the right pane, right-click the RefCount value (if none exists, right-click the right pane and click New and DWORD (32 bit) Value, then type RefCount and press Enter), and click Modify. d) Type 0 into the Value Data textbox and click OK. e) In the right pane, right-click the State value and click Modify. f) Type 0 into the Value Data textbox and click OK.
	5. Try logging on again! Close regedit and restart the computer. You should be able to logon now...

Channel Bonding Interfaces RedHat Enterprise

9.2.4. Channel Bonding Interfaces

Red Hat Enterprise Linux allows administrators to bind multiple network interfaces together into a single channel using the bonding kernel module and a special network interface called a channel bonding interface. Channel bonding enables two or more network interfaces to act as one, simultaneously increasing the bandwidth and providing redundancy.

To create a channel bonding interface, create a file in the /etc/sysconfig/network-scripts/ directory called ifcfg-bondN, replacing N with the number for the interface, such as 0.

The contents of the file can be identical to whatever type of interface is getting bonded, such as an Ethernet interface. The only difference is that the DEVICE directive is bondN, replacing N with the number for the interface. The NM_CONTROLLED directive can be added to prevent NetworkManager from configuring this device.

The following is a sample channel bonding configuration file:

Example 9.1. Sample ifcfg-bond0 interface configuration file

DEVICE=bond0
IPADDR=192.168.1.1
NETMASK=255.255.255.0
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
NM_CONTROLLED=no
BONDING_OPTS="bonding parameters separated by spaces"

After the channel bonding interface is created, the network interfaces to be bound together must be configured by adding the MASTER and SLAVE directives to their configuration files. The configuration files for each of the channel-bonded interfaces can be nearly identical.

For example, if two Ethernet interfaces are being channel bonded, both eth0 and eth1 may look like the following example: 

 

DEVICE=ethN
BOOTPROTO=none
ONBOOT=yes
MASTER=bond0
SLAVE=yes
USERCTL=no
NM_CONTROLLED=no

In this example, replace N with the numerical value for the interface.

Support for bonding was added to NetworkManager in Red Hat Enterprise Linux 6.3. See Section 9.2.1, “Ethernet Interfaces” for an explanation of NM_CONTROLLED and the NM_BOND_VLAN_ENABLED directive.

AnyConnect and VPN Client

AnyConnect : SSL or Web VPN,  Clientless VPN on ASA 5505
VPN Client  : Easy VPN Client

How to Change the Listening Port for Remote Desktop

This article describes how to change the port that Remote Desktop listens on. Note The Remote Desktop Connection Client for the Mac supports only port 3389. 3389 is the default port.

Edit Steps

1. 1
   Start Registry Editor.
   
   
   
2. 2
   Locate and then click the following registry sub-key:
3. 3
   HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\
   
   
   
4. 4
   RDP-Tcp\PortNumber
   
   
   
5. 5
   On the Edit menu, click Modify, and then click Decimal.
   
   
   
6. 6
   Type the new port number, and then click OK.
   
   
   

How To Check Your Windows 7 Licence Information

This is an easy way to check your Windows 7 license information using the command prompt, especially handy if you're using an evaluation copy of Windows 7

NOTE: Using winver alone doesn't necessarily display the correct expiration date, nor the license status


1. Open a command prompt by pressing the Winkey+R, typing cmd into the address bar and hitting enter.



2. In the command prompt type;
slmgr and hit enter.



A Windows Script Host will pop up informing you of an invalid combination of command parameters.
In the script host you'll be shown Global Options, Advanced options, Volume Licensing: Key Management Service (KMS) Client options, Volume Licensing: Token-based Activation Options & Volume Licensing: (KMS) Options.
For most, the global options will do. The most frequently used command will be to check the licence status and expiration date.


3. To display the current license information type into the command prompt;
slmgr /dli and hit enter.



4. To display detailed information on the current license type into the command prompt;
slmgr /dlv and hit enter.



5. To display the expiration date for the current license type into the command prompt;
slmgr /xpr and hit enter.



If an evaluation copy of Windows is being used, the rearm command may be used up to three times to extend the grace period. Grace period, and rearm counts are displayed by using slmgr /dlv



6. To rearm Windows and extend the grace period, in the command prompt, type;
slmgr /rearm and hit enter.



7. Restart your system to apply the changes.