Archive

Archive for the ‘Windows Client’ Category

AD RMS Troubleshooting: Reset the Client (MSIPC)

February 23, 2017 Leave a comment

In the course of troubleshooting the MSIPC rights management it may be beneficial to reset the client. The reset process removes the pertinent registry settings and files. This reset applies to the logged on user. Other users on the same machine are not reset.

The steps are as follows.

  1. Exit running Office applications.
  2. Delete existing registry entries.
  3. Clear existing licenses, GICs (RACs), and etc.
  4. Reproduce the issue.

NOTE: Feel free to export the DRM registry key before deleting it. Moving the entire MSIPC directory to another location or renaming it may be done instead of deleting it.

Delete the RMS registry settings for the user.

  1. Open regedit.exe.
  2. Navigate to HKCU\Software\Microsoft\Office\XXX\Common\DRM.
    XXX is the current Office version. 15.0 is Office 2013, 16.0 is Office 2016. There may be multiple versions listed (which is normal). Picking the highest is usually the correct one.

    1. Delete the DefaultServer and DefaultServerURL values.
  3. Navigate to HKCU\Software\Classes\Local Settings\Software\Microsoft\MSIPC.
    Note: this step resets the template distribution settings to default.

    1. Delete the <Server name> key that corresponds with desired RMS server/cluster.

Clear the existing licenses, GICs (RACs), and etc.

  1. Use one of the following methods to open the user MSIPC directory.
    1. Open a command prompt and enter the following commands.
      1. Cd %localappdata%
      2. Start . (the command is the word Start followed by a “period” and the enter key.
    2. In the “Search programs and files” dialog type %localappdata%
  2. In the AppData\Local directory navigate to the Microsoft directory.
  3. Delete the MSIPC directory.

NOTE: The CLC*.drm file may be too long for either Explorer or the command prompt to delete. Explorer reports a “destination path too long” error and the command prompt says “the file name or extension is too long.” In this case we may use robocopy.exe to move the MSIPC directory to another location.
I created a C:\Temp directory and used the following command.
robocopy “C:\Temp” %localappdata%\Microsoft\MSIPC /mir

Screenshots

Using the start menu to navigate to the MSIPC directory

Sample contents of the MSIPC directory for the curious.

Reference: https://social.technet.microsoft.com/wiki/contents/articles/19251.ad-rms-troubleshooting-reset-the-client-msipc.aspx#Delete_the_RMS_registry_settings_for_the_user

Advertisements
Categories: EMS, Windows Client

How to uninstall windows intune client

February 23, 2017 Leave a comment

It is not possible to uninstall the Windows Intune client from Programs and Features (for obvious reasons). Step by Step Guide describes how to do this.

There are 3 methods:

  1. Intune Administrator console – “retire the device”.
  1. Command line on the device
  • Open an admin command prompt
  • Navigate to C:\Program Files\Microsoft\OnlineManagement\Common
  • Run “ProvisioningUtil /UninstallAgents /WindowsIntune”

This will create a scheduled task and shortly uninstall all the agents.

3. Download and run the Microsoft uninstall script

Windows_Intune_AIS_Uninstall_Scripts_Extractor.exe

reference: http://gerryhampsoncm.blogspot.co.id/2013/08/uninstall-windows-intune-client.html

Categories: EMS, Windows Client

Azure Active Directory Connect Export profile error: stopped-server-down.


Kloud Blog

Originally posted on Lucian’s blog over at clouduccino.com.

Follow Lucian on Twitter @LucianFrango.


A couple of weeks ago I deployed Azure AD Connect in production. It was a relatively smooth process. The wizard did most of the work which was great. There was a few hiccups (blog post) along the way, which, in most cases is expected if the problems are not so serious.

Fast forward to my second install of the latest and greatest sync service for Azure AD and Office 365 cloud identities and we have problem no. 2. This time, though, I can say that the process ran through allot smoother. There was no real errors. Things were looking straight great and I was looking at my next task with some enthusiasm.

However, come 8.30ish this morning and going over the AADConnect server once more for peace of mind, I had noticed that the…

View original post 442 more words

Categories: Windows Client

Disable Certificate Revocation Check

April 28, 2016 Leave a comment

 

There may be several scenarios where we may experience long wait time for the services or application to start.
This problem is when the server has no internet access or when the server has limited internet access. One of the reasons for this issue is that the routine check of the certificate revocation list for .NET assemblies. Let’s see as how to disable the certificate revocation check in this article.

There are two ways to turn of the certificate revocation while doing a rollup update.

Turn off certificate revocation check in Internet Explorer:

Step 1: In Internet Explorer => go to Tools =>Internet Options => Advanced tab

Step 2: In the Security section => uncheck or clear the box for:

“Check for publisher’s certificate revocation”

“Check for server certificate revocation”

Step 3: Save Settings.

Turn off certificate revocation check in registry:

Step 1: Open registry editor => Navigate to the following key: HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionWinTrustTrust ProvidersSoftware Publishing

Step 2: Change Value “State” to 146944 Decimal or 0x00023e00 Hexadecimal

This will disable the certificate revocation check & the rollup update will complete successfully. However, disabling the revocation check in production environment is not recommended. We have to make sure to enable it back. Certificate revocation checking protects our clients against the use of invalid server authentication certificates either because they have expired or because they were revoked.

Turn on certificate revocation check in Internet Explorer:

Step 1: In Internet Explorer => go to Tools =>Internet Options => Advanced tab

Step 2: In the Security section => check the box for:

“Check for publisher’s certificate revocation”

“Check for server certificate revocation”

Step 3: Save settings.

Turn on certificate revocation check in registry:

Step 1: Open registry editor => Navigate to the following key: HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionWinTrustTrust ProvidersSoftware Publishing

Step 2: Change Value “State” to 146432 Decimal or 0x00023c00 Hexadecimal.

Ref: http://msexchangeguru.com/2015/10/07/certificate-revocation-check/

 

Categories: Internet, Windows Client

How to import all DNS records from one server to another

April 27, 2016 Leave a comment

itprofessors

sometimes when migrating the domain from one domain to a new domain , you have to export all the DNS records from the source domain and import them into the target domain.

Here is a quick way of doing it:

Part A – Export the DNS records from the source server.

on the source DNS server

1.open DNS managment.

2.right click on the relevant zone->export list

3.save the file , and copy it to the target server.

The output should look like this

in this example i would want to export only the static DNS records, so i will filter column D  and leave only the static records.

Part B – Import the static entries into the target server

1.We will use DNSCMD to import the DNS entries we exported in Part A.
2.Open the file you saved in step A, in Excel
3.Delete any of the rows that you…

View original post 253 more words

Categories: Windows Client

Enable Ediscovery inplace hold and Litigation hold office365 using powershell

April 27, 2016 Leave a comment

before enable ediscovery inplace hold and litigation hold you must to connect Microsoft Online using Windows Azure Active Directory Module for windows Powershell,

here step by step to enable ediscovery in place hold and litigation hold

  1. On your local computer, open Windows PowerShell and run the following command.
    $UserCredential = Get-Credential
  2. Run the following command.
    $Session = New-PSSession -ConfigurationName Microsoft.Exchange 
    -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential 
    $UserCredential -Authentication Basic -AllowRedirection
    
  3. Run the following command.
    Import-PSSession $Session
  4. Enable Edisocver Inplace hold
    New-MailboxSearch "deby sandra" -sourcemailboxes "deby.sandra@demagnum.com" 
    -estimateonly -InplaceHoldEnabled $true
  5. Start Mailbox-search
     Start-MailboxSearch -Identity "deby sandra"
  6. Please confirm Yes
  7. enable Litigationhold
    Set-Mailbox deby.sandra@demagnum.com -LitigationHoldEnabled $true

    please makesure that ediscovery in hold and litigation hold enable in the portal office365,

  8. Check Inplace hold27-04-2016 10-58-34

Check Litigation Hold Enabled27-04-2016 11-06-47

here for example command to enabled ediscovery hold and litigation hold

27-04-2016 11-09-33

add -force to disable prompt confirmation

Ref: https://technet.microsoft.com/en-us/library/jj984289(v=exchg.160).aspx

Categories: Office 365, Windows Client

Office 365: Script to get detailed report of assigned licenses

April 25, 2016 Leave a comment

Microsoft Exchange & Office 365

It’s very common to see Office 365 administrators asking in the community “How can I get a detailed report of the licenses i have assigned on Office 365?

Well it will depend on how detailed you want the report. I’ll detail here two solutions.

1 – Get a report of all licensed users and the AccountSKUId name

To run this report you need to open the Windows Azure Active Directory Module for Windows Powershell, and connect to Office 365. Once connected run the following cmdlet:

Get-MSOLUser -All | select userprincipalname,islicensed,{$_.Licenses.AccountSkuId}| Export-CSV c:userlist.csv -NoTypeInformation

The above command lists ALL users and not just the ones that have a license. See the output CSV file below. There are ways of filtering the output (i.e export only licensed users), but i will keep this post simple. Let me know if you need something more elaborated.

1

2 – Get a detailed report of…

View original post 418 more words

Categories: Windows Client