Unable Access Second Partition After Formatting Primary Partition

Issue

On a whole disk encrypted a disk with two partitions, the second partition is inaccessible after formatting the primary partition without decrypting the disk.  

Warning: Do not re-encrypt the C: Drive as this will result in overwriting the session key and PGPWDE01 file which contains the drive encryption information and makes the disk unrecoverable.

Environment
  • 2 partitions on an internal hard disk (C: and D: )
  • Both partitions are PGP Whole Disk Encrypted
  • The C: partition is formatted without decrypting the drive
Solution

To resolve this issue, you must attached the disk to another computer with PGP Desktop installed. Then use the pgpwde command line interface to decrypt the disk.

Use the following steps:

1. Open a Windows Command Prompt.

2. Change to the following directory C:\Program Files\PGP Corporation\PGP Desktop

3. Type pgpwde –recover -d 1 –passphrase “your passphrase" and press Enter.

(Assuming that the D: drive is the disk number “1”)

Drive Encryption Diagnosis and Recovery

Drive Encryption Diagnosis and Recovery – Symantec Drive Encryption & PGP Whole Disk Encryption

http://www.symantec.com/business/support/index?page=content&id=TECH149679

Issue

This article provides tools and steps to diagnose and recover disks that are encrypted with Symantec Drive Encryption (previously PGP Whole Disk Encryption). 

Solution

Section 1 describes some symptoms that users with encrypted disk problems may encounter.  Section 2 provides procedures for using the PGPWDE command line interface. Section  3 details use of the Recovery Disk.

Note: If a system hard disk has been “fully" decrypted, and will not boot, make sure to slave the disk and backup all your data, or use bit-by-bit copy of the disk. Connect the hard disk back to system and run the fixmbr command from the Windows Recovery Console from a Windows XP installation CD.

SECTION 1 – Symptoms

On rare occasions internal or external disks that are encrypted may experience the following issues:

  • Inability to decrypt or read the contents of a secondary or non-system disk.
  • System displays “Error loading operating system_" after entering the passphrase at the PGP BootGuard screen.
  • Master Boot Record (MBR) corruption causing the system to no longer boot.
  • After starting the system with the hard disk encrypted to a passphrase and an eToken, valid passphrases are not accepted.

1. Users able to access their encrypted disk from Windows should proceed to Section 2.
2. Users unable to access their disk from Windows or who are unable to boot should proceed to
Section 3.

SECTION 2 – PGPWDE Command Line

The following commands will help diagnose and decrypt the disk. Other commands can be listed by typing pgpwde –help.
1. To begin working with the PGPWDE command line tool, open a command prompt and change to the PGP installation directory (default directory shown) C:\Program Files\PGP Corporation\PGP desktop.
2. To list all installed hard disks in the system type: pgpwde –enum. Entering this command displays a list of disks which the following steps reference.
3. Type pgpwde –status –disk 1. In the command, substitute the PGP WDE disk number listed in the previous step for the number 1 if it is different. The output of this command tells you whether the disk is still encrypted. 

  • If the disk is not encrypted, “Disk <number> is not instrumented by bootguard" will be the output.
  • If the disk is encrypted, the output will display:
    “Disk <number> is instrumented by Bootguard."
    The total number of sectors.
    A Highwater value (number of sectors encrypted).
  • Whether the current key is valid.

4. Type pgpwde –list-user –disk 1. This provides the user information contained on the disk. This will help in multi-user environments to determine which user passphrase was used for Drive Encryption.
5. Type pgpwde –decrypt –disk 1 –passphrase {MYPASSWORDHERE}. This will start the decryption process. To view progress, type the status command listed in step 3 and note the Highwater number. This number will get smaller and smaller as the number of sectors encrypted decreases. 

6. In case if your primary partition was formatted and your secondary partition is still encrypted, you may try to recover it by following TECH170574.

SECTION 3 – Using Recovery Disk Images (bootg.iso or bootg.img)

Warning: Use of the recovery disks should be used as the last step when attempting recovery.  Should there be a power loss while decrypting with the recovery disk, the result to the disk could be fatal and non-recoverable. It is also highly recommended to use the latest recovery disk available for the version you are running.
Recovery Images can be obtained by following the links below:

Windows

Mac OS X

Caution: Users with extended partitions on their hard disks that were encrypted should ONLY use the latest available Recovery disk for your version. Prior versions could cause these partitions to no longer be visible to Windows after fully decrypting the disk.
Once you have started to decrypt a disk or partition using a recovery CD, do not stop the decryption process. Depending on the size of the disk being decrypted, this process can take a long time. A faster way to decrypt the drive is to use another system that has the same version of Encryption Desktop\PGP Desktop installed on it.

Use the Recovery Disk with the following instructions if experiencing blue screen failures at boot up:
1. Boot the system with the recovery disk.
2. Do not continue with the normal sequence of entering a passphrase.
3. Go to the “advanced" panel.
4. This message “PGPWDE record inconsistency on 1 disk(s) was found and fixed" might be displayed. If this message is seen, the BSOD (blue screen failure) will be fixed.
5. Return back to the previous screen and continue to boot from the recovery CD. Rebooting without the Recovery Disk in the drive also works.

Use the Recovery Disk with the following instructions should the system not boot into Windows for any other reasons:

The Symantec Encryption Desktop for Windows User’s Guide provides instructions for creating recovery disks. 

  1. Boot the system with the recovery disk.
  2. When prompted, press any key to continue. Drive Encryption Recovery searches for user records and prompts to press any key when the records are found.
  3. Press any key to continue.
  4. On the PGP BootGuard screen, enter the passphrase and user name, if required.
  5. Press D to decrypt the drive. Drive Encryption Recovery starts decrypting your disk.

Note: Decrypting using a Recovery disk might take considerably more time than it does from within Windows.

DLP 12.5 無法偵測部分符合的 IDM 事件

DLP 12.5 在【系統】→【代理程式】→【代理程式組態】→【代理程式設定】→【進階代理程式設定】中,Detection.TWO_TIER_IDM_ENABLED.str 的參數值預設是【off】

表示 DLP 12.5 預設

(1) IDM 的偵測是在用戶端進行,Endpoint 與 Detection Server 間並非持續性的連線狀態 (Interval time 約 15 分鐘 )

(2) IDM 事件可以攔阻

(3) 偵測與攔阻的前提是相符率必須是 100%

(4) 無法偵測或攔阻部分相符的事件

 

若您需要偵測部分相符的事件請您參照以下畫面將 Detection.TWO_TIER_IDM_ENABLED.str 的參數值改為【on】

(1) 此設定下表示 IDM 的偵測是 forward 至 Detection Server 進行

(2) 此設定下無法攔阻部分相符的事件

(3) 也無法攔阻100% 相符的事件

1. 在【系統】→【代理程式】→【代理程式組態

image

2.【代理程式設定】

image

3.【進階代理程式設定】

image

4.將 Detection.TWO_TIER_IDM_ENABLED.str 的參數值改為【on】

image

5. 由於 DLP 12.5 開始,Agent 並非持續與 Detection Server 連線,因此相關事件無法即時回傳主控台,您必須再更改以下參數

[DLP 12.5] Incidents delay. Takes longer to show on Incidents reports.  Symantec Connect

http://www.symantec.com/connect/forums/dlp-125-incidents-delay-takes-longer-show-incidents-reports#comment-10466151

image

6. 請至【管理】→【資料設定檔】→【已建立索引的文件】

image

 

7. 【重新建立索引】

image

8. 重啟 Enforce server

Symantec DCS Agent 健康狀態說明

問題:

  • 針對 SDCS Agent 端 Health 狀況說明

版本:

  • 6.0

說明:

image

Agent Health 在 Assets「資產」頁面的 Agent Health「代理程式健康狀態」欄中,會以綠色、黃色或紅色圓形圖示表示。

  • 綠色圖示表示 Agrnt 在線上。
  • 黃色圖示表示 Agent 可能離線。
  • 紅色圖示表示 Agent 已經離線。

黃色與紅色預設值分別用於實體環境及虛擬環境。Agent Health 圖示的顏色是按照以下規則決定:

  • 綠色:如果上一次 Contact Time 或 Last event time 與黃色間隔秒數相加,所得時間大於目前時間。
  • 黃色:如果上一次 Contact Time 或 Last event time 與黃色間隔秒數相加,所得時間小於目前時間,而上一次聯絡時間或最後事件時間與紅色間隔秒數相加,所得時間大於目前時間。
  • 紅色:如果上一次 Contact Time 或 Last event time 與紅色間隔秒數相加,所得時間小於目前時間。

 

代理程式健康狀態的逾時設定如下:

1. 於 Asset 頁面,以滑鼠右鍵點選 Agent,選取「Propertise」。

image

2. 點選「Configure Health」,接著可以修改設定。

image

image

 

為避免代理程式離線和連線時產生大量網路流量,全系統流量控制選項可將狀態變更事件彙總成單一事件。

選取「Admin」頁籤,點選「Settings」接著選取「System Settings」,最後選取「Agent Settings」頁籤。

image

代理程式狀態變更事件數的臨界值,此數目會引發產生單一彙總狀態變更事件,而不是大量個別代理程式事件。若因網路中斷而一次影響大量代理程式,此設定有助於限制產生的無意義事件(及任何相關警示)數目。預設:25。

安裝好 PGP Desktop E-mail 後,outlook 無法發信出現【PGP Universal service not available】

安裝好 PGP Desktop E-mail 後,outlook 無法發信出現【PGP Universal service not available】

image

請將 Outgoing Mail Server (SMTP) 中,SSL/TLS 下拉改選【Do not attempt】即可解決

[點圖可放大]

image

 

【其他的除錯步驟】

1.Exit PGP Services 後,確認 Outlook 寄信是否正常,若仍不正常則可能是原始 mail client 設定有問題
 
image

 

2. 刪除重建 PGP Desktop E-mail service

image

3.提供用戶端 log

image

4.Enterprise Support – Symantec Corp. – Troubleshooting: PGP Messaging Services for PGP Desktop 10 for Windows
http://www.symantec.com/business/support/index?page=content&id=TECH149647

 

By default, PGP Desktop automatically determines your email account settings and creates a PGP Messaging service that proxies messaging for that email account.

Because of the large number of possible email account settings and mail server configurations, on some occasions a messaging service that PGP Desktop automatically creates may not work quite right.

 

If PGP Desktop has created a messaging service that is not working right for you, one or more of the following items may help correct the problem:

Verify that you can both connect to the Internet and send and receive email with PGP Services stopped. To do this:
Right-click the PGP Desktop Tray icon and select Stop PGP Services from the list of commands.

Note: You should always restart your email client after starting or stopping PGP Services.
Read the PGP Desktop Release Notes for the version of PGP Desktop you are using to see if your problem is a known issue.

Make sure SMTP authentication is enabled for the email account (in your email client). This is recommended for PGP Desktop to proxy your messaging. If you only have one email account and you are not using PGP Desktop in a PGP Universal Server-managed environment, then SMTP authentication is not needed. It is required when using a PGP Universal Server as your SMTP server, or when you have multiple email accounts on the same SMTP server.

Open the PGP Log to see if the entries offer any clues as to what the problem might be.

If SSL/TLS is enabled in your email client, you must disable it there if you want PGP Desktop to proxy your messaging. (This does not leave the connection to and from your mail server unprotected; by default PGP Desktop automatically attempts to upgrade any unprotected connection to SSL/TLS protection. The mail server must support SSL/TLS for the connection to be protected.)

If either Require STARTTLS or Require SSL is selected (in the SSL/TLS settings of the Server Settings dialog box) your mail server must support SSL/TLS or PGP Desktop will not send or receive any messages.

If your email account uses non-standard port numbers, make sure these are included in the settings of your messaging service.

If PGP Desktop is creating multiple messaging services for one email account, use a wild card for your mail server name.

Delete the PGP Messaging service that is not working correctly and send/receive email. PGP Desktop regenerates the messaging service.
If none of these items help correct the problem, try manually creating a PGP Messaging Service.

5.
http://www.symantec.com/connect/forums/not-working-outbound-mail-encryption-outlook-2010-pgp-1021

Please reread the PGP Release Notes for any known conflict or settings adjustments that may be needed for your system.

Although I don’t see Norton 360 specifically mentioned, the following quote may offer guidance that might also help with Norton 360 use.

Symantec Norton AntiVirus 9.x through 10.x, Symantec Norton Internet Security 2003, Symantec Norton Internet Security 2004
Disable email scanning.
For Norton Internet Security users, disable Norton Privacy Control and Spam Alert.
Disable SSL/TLS in Server Settings in PGP Desktop and PGP Universal Satellite. (In PGP Desktop, select the PGP Messaging Control Box and then choose Messaging > Edit Server Settings. For SSL/TLS, select Do Not Attempt. In PGP Universal Satellite, on the Policies tab, select Ignore SSL/TLS.) These versions of Norton AntiVirus prevent all mail clients from using SSL/TLS, regardless of the use of PGP software.

Symantec Norton AntiVirus 11.x through 12.x, Symantec Norton Internet Security 2005, Symantec Norton Internet Security 2006
No special configuration required for MAPI email.
When using POP email, enable Auto-Protect and disable the Anti-Spam and Email Scanning options. Auto-Protect, which is enabled by default, provides protection against viruses in email messages when the message is opened.
Disable SSL/TLS in Server Settings in PGP Desktop or PGP Universal Satellite. (In PGP Desktop, select the PGP Messaging Control Box and then choose Messaging > Edit Server Settings. For SSL/TLS, select Do Not Attempt. In PGP Universal Satellite, on the Policies tab, select Ignore SSL/TLS.) These versions of Norton AntiVirus prevent all mail clients from using SSL/TLS, regardless of the use of PGP software.

針對 SEPM 弱點掃描 CVE-2007-6750

問題:

  • 針對 SEPM 進行弱點掃描發現 CVE-2007-6750

版本:

  • 12.1.2 ~ 12.1.3

解決方案:

如果無法立即升級,可先進行下述設定。這種解決方法僅適用於上面提到的版本(12.1.2 ~ 12.1.3)。

如果版本屬於 12.1.2 以前,應該升級直接到 12.1.4 或更高版本。

1. 請先行下載 mod_reqtimeout.so

2. 將文件複製到 %SEPM_Install_Dir%\apache\modules。
(注 ​​:在大部份的系統中,預設的 SEPM 安裝路徑是 C:\Program Files(x86)\Symantec\Symantec Endpoint Protection Manager)

3. 用記事本開啟 %SEPM_Install_Dir%\apache\conf\httpd.conf,於檔案最後修改並增加下面內容

LoadModule reqtimeout_module modules/mod_reqtimeout.so
<IfModule reqtimeout_module>
RequestReadTimeout header=20-30,MinRate=256 body=100-120,MinRate=512
</IfModule>

4. 重新啟動 Symantec Endpoint Protection Manager Webserver 的服務。

可參考 http://www.symantec.com/business/support/index?page=content&id=TECH205208

[SEP]Symantec Endpoint Protection Manager 主控台升級

問題:

  • 如何將 Symantec Endpoint Protection Manager 主控台升級版本

版本:

  • 11.0.X
  • 12.1.X

解決方案:

1. 登入Symantec Endpoint Protection Manager。

image

2. 點選右上角「說明」,接著點選「關於」。

image

3. 看到目前使用版本為:12.1.2015.2015。

image

4. 開啟新版的安裝程式。

image

5. 點選「安裝Symantec Endpoint Protection」。

image

6. 點選「安裝Symantec Endpoint Protection Manager」。

image

7. 準備進行升級管理伺服器與主控台,點選「下一步」。

image

8. 確認下列應用程式已關閉,接著點選「下一步」。

image

9. 點選「我同意」,接著點選「下一步」。

image

10. 點選「立即備份資料庫」。(若已備份可忽略)

image

11. 開始進行資料庫備份,點選「是」。

image

12. 點選「完成」。

image

13. 點選「備份」。

image

14. 確認是否要「備份日誌」,接著點選「是」。

image

15. 備份資料庫中。

image

16. 備份完成,點選「確定」。

image

17. 備份完畢,點選「結束」。

image

18. 點選「完成」退出精靈。

image

19. 再次點選「安裝Symantec Endpoint Protection Manager」。

image

20. 準備升級管理伺服器與主控台,點選「下一步」。

image

21. 確定下列應用程式已關閉,接著點選「下一步」。

image

22. 授權許可協議,點選「我同意」,接著點選「下一步」。

image

23. 安裝準備完成,接著點選「安裝」。

image

24. 正在安裝中。

image

25. 安裝完成,準備升級,點選「下一步」。

image

26. 確認升級伺服器至剛剛所安裝的版本,接著點選「下一步」。

image

27. 確認通訊埠號,接著點選「下一步」。

image

28. 確認升級伺服器時,是否執行LiveUpdate,接著點選「下一步」。

image

29. 伺服器升級中。

image

30. 升級成功,接著點選「下一步」。

image

31. 升級成功,確認是否要「啟動Symantec Endpoint Protection Manager」,接著點選「完成」。

image

32. 登入Symantec Endpoint Protection Manager。

image

33. 點選右上角「說明」,接著點選「關於」。

image

34. 可看到版本已經更新為12.1.5(12.1 RU5),代表更新完成。

image