ITEXVN

  Lỗi này phần lớn do đồng hồ giờ trên server không đồng bộ với giờ thế giới. Tiến hành đồng bộ lại giờ cho đúng là xong.

Nguyên nhân do DSM 7 yêu cầu bảo mật cao hơn nên các thiết bị client cũ cần nâng cấp phiên bản mới nhất thì mới truy cập được. Nếu thiết bị client quá cũ không hỗ trợ thì buộc phải vào DSM hạ level bảo mật xuống như sau: STEP 1 Go to  Control Panel  /  File Services  /  SMB  tab /  Advanced Settings . Follow the instructions in the image below. STEP 2 After you click  Advanced Settings  on  STEP 1 , a new pop up window will open. Click on the  Others  tab then select  Enable NTLMv1 authentication . Click  Save . Follow the instructions in the image below. STEP 3 After you click Save on  STEP 2 , a new warning pop up window will open. Click  Yes . Follow the instructions in the image below. Nguồn: https://mariushosting.com/fix-synology-dsm-7-smb-clients-get-disconnected/

 CẤU HÌNH MESSAGE TRACKING & LOG TRÊN EXCHANGE 2010 Có 2 loại log: - Message Tracking log : ghi nhận mail in/out qua lệnh gửi trực tiếp. Mặc định là lưu 30 ngày Ta có thể điều chỉnh lại số ngày, kích thước tối đa của file log, thư mục log - Protocol Log : ghi nhận log của các connector (Send, Receiver, Relay) - Đường dẫn mặc định Lệnh đổi đường dẫn lưu log: Set-TransportServer “TRANSPORT SERVER NAME” -ReceiveProtocolLogPath “D:\New SmtpReceive Log File Directory” Set-TransportServer “TRANSPORT SERVER NAME” -SendProtocolLogPath “D:\New SmtpSend Log File Directory” - EXTRA: + Tìm kiếm message Get-MessageTrackingLog -ResultSize Unlimited | Where-Object {$_.Recipients -like "*@domain.com"} | Select-Object Timestamp, Sender, {$_.Recipients}, MessageSubject, EventId | Export-Csv -Path "C:\Reports\RecipientDomainReport.csv" -NoTypeInformation

  Do services Microsoft Exchange Address Book bị stop Start lại service này là OK

  A while back i wrote a post about data deduplication in 2012…. generally a very good feature, but as that specific post talked about, there was a collection of .iso and compressed data where not only did dedup not save me anything, it actually used up more space in the dedup folder than the orginal data size (which i found a little odd) Today i got around to doing something about this and found Disabling data deduplication (via GUI or powershell) only stops further deduplication from occuring – but data that has already been deduplicated will remain deduplicated In order to “move” (re-hydrate ?) the data back to the original files and out of the deduplication store, use the powershell command  start-dedupjob -Volume <VolumeLetter> -Type Unoptimization You can check the status on where this is at by using  get-dedupjob , or, i like using TreeSize which shows the size on disk of specific files…. including the deduplication chunks At this stage – i noticed the o...

 Move by command (Allow large data loss) New-MoveRequest -Identity UserID -AcceptLargeDataLoss -BadItemLimit 200 -TargetDatabase DB-MB-EX03 -ArchiveTargetDatabase DB-Archive-EX03

 Fatal error MapiExceptionNotFound has occurred. Error details: MapiExceptionNotFound: Unable to synchronize manifest. (hr=0x8004010f, ec=-2147221233) This error will appear due to mailbox corruption to eliminate the above error need repair the mailbox  execute the following shell command then clear the move request and initiate again move request   New-MailboxRepairRequest -Mailbox userID -CorruptionType SearchFolder, AggregateCounts, ProvisionedFolder, FolderView

  Prerequisites An RDB must be created. The database and log files containing the recovered data must be restored or copied into the RDB folder structure that was created when the RDB was created. The database must be in a clean shutdown state. Because an RDB is an alternate restore location for all databases, all restored databases will be in a dirty shutdown state. You can use Eseutil /R to put the database in a clean shutdown state. (Text copied from technet) Step 1 Start up DPM 2010 and go to the Recovery section, select the appropriate database, also make sure to select a date very the user mailbox should be recovered from. Right click the database and select “Recover”. Check so that the date and time are correct and press “Next”. Select “copy to network folder” and select “Next”. Copy destination, select the appropriate server and folder press “Next”. On the next selection window we got a very nice option to select, it’s called “Bring the database to a clean state after copyi...

  Optimize Storage In Windows To Optimize the Storage in Windows Server 2012, 2012 R2, 2016 and 2019 Windows PowerShell cmdlet is available. It provides the ability to manually perform actions like TRIM, Defragment, etc. TRIM – The parameter is  ReTrim  which generates TRIM and Unmap hints for all currently unused sectors of a volume. Defrag – The parameter defrag/L performs the same TRIM (-ReTrim) as the Optimize-Storage PowerShell cmdlet