HOW TO UNLOCK PASSWORD PROTECTED PPT FILE (READ ONLY)

First of all you have a password protected PPT file and after that apply the following step:

1) You have to change file extension. For example test.pptx to test.zip

i) there are two way to change the extension as follow:
a) directly double click on the particular file.
b) through command prompt.

2) After changing the extension, open the .zip folder and find presentation.xml file.
(i)    test.zip\ppt

(ii)   copy that presentation.xml file.
(iii)  open in notepad and search “crypt” and delete in between the quotes
“</p:defaultTextStyle><p:modifyVerifier cryptProviderType=”rsaFull” cryptAlgorithmClass=”hash”cryptAlgorithmType=”typeAny” cryptAlgorithmSid=”4″ spinCount=”50000″saltData=”IGD5MUl2SfTAX2r8Ma/sNw” hashData=”Ve9wEKhZfdyqOTF2IlkrbekLv9Y”cryptProvider=”” algIdExt=”0″                           algIdExtSource=””cryptProviderTypeExt=”0″cryptProviderTypeExtSource=””/>”.
(iv)  do not delete “</p:presentation>” in the end of the xml file.
(v)   save the file and replace the original file into the zip folder.
(vi)  rename .zip folder to .pptx

3) Here you go the file is editable and unprotected.

Advertisements

Error “unhandled exception” when you try to login to ESXi web interface from chrome browser

Problem:

When you try to login to the esxi web interface, you receive a following message.

Unhandled Exception
Unfortunately, we hit an error that we weren't expecting.
The client may continue working, but at this point, we recommend refreshing your browser and submitting a bug report.

This occurs when you are logging in from a chrome browser. If you login from an Microsoft Edge browser, you are able to login. When you login to the system, if you type in the userid and password and press enter you receive the message. If you click on the login button with a mouse (instead of typing enter), you do not receive the error message and you are able to login properly.

Solution:

Update the ESXi Embedded Host Client. Click here to get the latest Embedded Host Client. Click on the Instructions tab to learn how to run the update.

How to install .NET Framework 3.5 on Windows Server 2016

The solution to “The source files could not be found” when installing .NET Framework 3.5 on Server 2012 (or Windows 8)  is to:

  1. Pop in the DVD (or the ISO for the DVD)
  2. Start the ADD ROLES AND FEATURES Wizard and click the obvious choices up until the CONFIRMATION screen
  3. on the CONFIRMATION screen of the ADD ROLES AND FEATURES WIZARD, you need to click the SPECIFY SOURCE link (tiny link at the bottom of the window)
  4. Point the source path to D:\sources\sxs\ (obviously change D:\ to whatever your DVD drive letter is)

Also note that if you download the .NET 3.5 installer from the web and then try to run it, the install will error out with:

Install from roles and features

For more detail read MS KB2734782:

In Windows 8 and in Windows Server 2012, the .Net Framework 3.5 is a Feature on Demand. The metadata for Features on Demand are included in Windows 8 and in Windows Server 2012. However, the binaries and other files associated with the feature are not included. When you enable the feature, Windows tries to contact Windows Update to download the missing information to install the feature.

Windows 10 Audit Mode

To get Windows 10 ready for imaging, use  the audit mode prior to imaging. After you enter the audit mode, you can install device drivers, custom software etc. Then you can create your image for deployment.

Boot to audit mode manually (on a new or existing installation)

  • At the OOBE screen, press CTRL+SHIFT+F3.Windows reboots the computer into audit mode, and the System Preparation (Sysprep) Tool appears.

    Note
    The CTRL+SHIFT+F3 keyboard shortcut does not bypass all parts of the OOBE process, such as running scripts and applying answer file settings in the oobeSystem configuration pass.

See https://www.youtube.com/watch?v=m7YI3rtnZCA for more details on how the audit mode works.

Removing disconnected Mailboxes from Exchange 2010

Use Get-MailboxDatabase -Status | Select Name, DatabaseSize, AvailableNewMailboxSpace to find the database size, and available mailbox space.

 

This is a quick how to which will enable you to remove any disconnected mailboxes from exchange 2010, since the purge mailbox feature is no longer available.

6 Steps total

Step 1: Run a clean on your mailbox store

Perform the below command in order to run the Clean task on your exchange mailbox store, you need to do this via the Exchange Command Powershell

clean-mailboxdatabase “Mailbox Store Name”

Step 2: Get a list of disconnected mailboxes in your database

Then run the below command to get a list of mailboxes that are in a disconnected state

Get-MailboxStatistics -Database “Mailbox Store Name” | Where-Object {$_.DisconnectDate -Notlike $NULL} | FL DisplayName, DisconnectDate, MailboxGuid

Step 3: Results

You should now see a result similar to the below

DisplayName : USERMAN
DisconnectDate : 1-7-2010 16:00:48
MailboxGuid : def4aabd-2156-5857-858f-470efc3e6f28

Step 4: Gather maxboxguid

Take the MailboxGuid and copy it to Notepad. For easy modification.

The MailboxGuid is needed to remove the mailbox completely, use the below command to remove the mailbox

Step 5: Remove / Delete the mailbox/’s

Now run the below comand inserting the Mailboxguid that you want to remove, repeat the process if you have multiple mailboxes to remove

Remove-Mailbox -Database “Mailbox Store Name” -StoreMailboxIdentity def4aabd-2156-5857-858f-470efc3e6f28

you will now be prompted to confirm that you want to completely remove the mailbox, if you agree accept this prompt.

You can the re run the Get-MailboxStatistics above to check there are no disconnected mailboxes remaining.

Step 6: Verify

to verify the mailboxes are no longer there , re -run the command in step 2, hopefully this will now display zero results.

Job Done !

This now should have removed all mailboxes that were diassassociated with any user accounts.

 

Remote reboot command returns an error “Network path was not found”.

Problem: When you try to reboot a remote computer using the command shutdown -m \\remotepc -r -f command, you receive an error message telling you that the Network path was not found. You know the remote PC is accessible via ping.

Solution:

  1. Click Start, type regedit in the Start Search box, and then click regedit.exe in the Programs list.
  2. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system
  3. On the Edit menu, point to New, and then click DWORD Value.
  4. Type LocalAccountTokenFilterPolicy for the name of the DWORD, and then press ENTER.
  5. Right-click LocalAccountTokenFilterPolicy, and then click Modify.
  6. In the Value data box, type 1, and then click OK.
  7. Exit Registry Editor.

How to delete Windows 10 bloatware so you can run sysprep

When you run sysprep under Windows 10 (Windows 8/8.1) you receive an error message saying that Sysprep was not able to validate your Windows installation.  Review the log file at %Windir%/System32\Sysprep\Panther\setupact.log for details. When you look at the log file, the message tells you that you can not run the sysprep because there is an application that was installed for a user, but was not provisioned for all users. The application name varies. This error occurs because the Windows 10 installs a lot of bloatwares that you must uninstall before you can run the sysprep.

The following scripts will help you uninstall the programs from your image, so you can run the sysprep.

First you can run the following script to see what provisioned apps are running.

Get-AppXProvisionedPackage -Online | Select PackageName

Use this command to remove the provisioned package.

Remove-AppXProvisionedPackage -Online | Select PackageName

Or use this command to remove all of them all at once.

Get-AppXProvisionedPackage -Online | Remove-AppxProvisionedPackage -Online

You may also have to run the following command to uninstall more packages.

Get-AppxPackage | Select Name, PackageFullName

You can then use the following command to remove the packages.

Get-AppxPackage PackageFullName | Remove-AppxPackage (You can use wildcards such as * for full name)

Use the following command to uninstall packages all at once.

Get-AppxPackage -allusers PackageFullName | Remove-AppxPackage (Removes allusers program)

Get-AppxPackage -user username PackageFullName | Remove-AppxPackage (Removes particular users program)

Get-AppxPackage | Remove-AppxPackage  (Removes all packages)