Friday, March 25, 2016

SlipStream Adobe Reader with Powershell to be deployed using SCCM or psexec

Deploying Adobe quarterly patch and the security update is pain specially when you have environment with no internet connection.

Note: You need to remove the older version of Adobe Reader in order be able to installed the slipstream version of Abode Reader.

Here is how I slipstream quarterly update with security patches

You can download the script from the TechNet Gallery.

To slipstream you need to download the following files from Adobe.
1. Base Installer ( eg. AdbeRdr11000_en_US.exe)
2. Quarterly Update
3. Security Patch

Ftp download link
ftp.adobe.com/pub/adobe/reader/win/11.x/11.0.06/en_US/AdbeRdr11006_en_US.exe

Apply the installer and patches in the following order:
Base Installer -> Quarterly Patch -> Security Patch
11.0.0->11.0.14 -> 10.1.15

Follow the steps to use the Power Shell Script:
1. Downloaded the necessary file(s) to a folder somewhere (should be a local drive or mapped network drive). I’ve downloaded AdbeRdr11006_en_US.exe to C:\Downloads. I’ll refer to this location as the Download folder in this post.
2. Create a folder called AIP. I’ve created it at C:\AIP and will refer to it as the TargetFolder.
3. Download the script from TechNet Gallery and extract it C:\Scripts.
4. Open an elevated PowerShell console, browse to C:\Scripts and run the following command:

.\New-AdobeReaderAIP.ps1 -FileName "AdbeRdr11006_en_US.exe" -DownloadFolder "C:\Download" -TargetFolder "C:\AIP"

5. The script will now start to slipstream Adobe Reader.




Copy the entire AIP folder to the destination computer and run the AcroReader.msi to install.


You can deploy remotely using psexec:

devices.txt contains the host names where you want to deploy it.

psexec @C:\adobe\devices.txt -h -u domain\username -p "password" -c xcopy /y /s "c:\AIP" c:\temp\update

psexec @C:\adobe\devices.txt -h -u domain\username  -p "password" msiexec.exe /i c:\temp\update\AcroRead.msi  /quiet /qn /norestart /l+ c:\temp\update-logs\log.txt

Wednesday, January 27, 2016

How to Move the Public Folder Hierarchy from Exchange 2003 Admin Group to the New Exchange 2010 Admin Group

This week as I was preparing to migrate Exchange 2010 to Exchange 2013 I found out that my previous predecessor did not decommission legacy Exchange 2003 properly.

When I ran get-exchangeserver, the older 2003 server was still showing. The public folder was still located in the Exchange 2003 Admin group.  When i ran get-routinggroupconnecter, it show the old connector.

Here is how to move the public Folder Hierarchy from Exchange 2003 Admin group to the New Exchange 2010 Admin Group:

Information

User is migrating from Exchange 2003 to Exchange 2007 or 2010 and wants to move the public folder hierarchy from the Exchange 2003 "First Administrative Group" to the new Exchange 2007/2010 "Exchange Administrative Group (FYDIBOHF23SPDLT)" to continue decommission the old Exchange 2003 Admin Groups.

Details

Use one of the following procedures to move the public folder hierarchy to a new Admin Group:
Using exchange system manager:
  1. Logon to the Exchange Server 2003 server and open the Exchange System Manager snap-in.
  2. Expand the Administrative Groups and right-click the Exchange Administrative Group (FYDIBOHF23SPDLT) , select New and select Public Folders Container .
  3. Then expand the old First Administrative Group , expand Folders and move the Public Folders tree to the Public Folders container you created in the previous step by dragging the Public Folders tree object and dropping it to Folders under Exchange Administrative Group (FYDIBOHF23SPDLT) .
Using ADSIEdit tool:
If already uninstalled all Exchange 2003 servers and do not have any Exchange System Manager elsewhere to use, same can be done with ADSIEdit.
  1. Create the new Public Folders container:
    1. Use ADSI Edit tool to locate and expand Exchange Administrative Group (FYDIBOHF23SPDLT) object, which can be found at:
      CN=Configuration,CN=Services,CN=Microsoft Exchange,CN=Organization,CN=Administrative Groups.
    2. Right-click the Exchange Administrative Group (FYDIBOHF23SPDLT) object, click New , and then click Object .
    3. In the Select a class list, select msExchPublicFolderTreeContainer , and then click Next .
    4. In the Value box, type Folder Hierarchies , click Next , and then Finish .
  2. Move the public folder hierarchy:
    1. Use ADSI Edit tool to locate the Public Folders object in Active Directory.
    2. CN=Configuration,CN=Services,CN=Microsoft Exchange,CN=Organization,CN=Administrative Groups,CN=Administrative group,CN=Folder Hierarchies,CN=Public Folders.
    3. In the right pane select CN=Public Folders , righ

Removing Exchange 2003 from the server object using ADSI edit.

  • CN=Administrative Groups
    CN=<Exchange 2003 admin group name>
    CN=Servers
    CN=<Exchange 2003 server name>
    You need to delete the Exchange 2003 server at this level to have it fully removed from your Get-ExchangeServer command results. 
After deleting the server, when I ran get-exchangeserver, it only showed 2010.

 To remove the routing group connector:

get-routinggroupconnector | remove-routinggroupconnector

Monday, January 18, 2016

No Certificate Templates could be found. You do not have permission to request a certificate from this CA

This morning I logged into my lab and I got an error while trying to access the Cert request enrollment.

 i received this error “No Certificate Templates could be found. You do not have permission to request a certificate from this CA, or an error occurred while accessing the Active Directory” .. That was so strange although i am sure i can access the certificate templates from the CA console and also the fact that i was using a Domain Admin account to issue the certificate.

I followed the link below to resolve the issue

http://theadminsguide.net/2012/08/29/no-certificate-templates-could-be-found-you-do-not-have-permission-to-request-a-certificate-from-this-ca/

Friday, December 18, 2015

I was trying to install Exchange Server 2013 CU11 on my lab exchange server. I encountered two errors.

1.  A Restart from a Previous Installing is pending

Resolution:

To remove an orphaned UpdateExeVolatile registry key value
  1. Open a registry editor, such as Regedit.exe or Regedt32.exe.
  2. Navigate to HKLM\SOFTWARE\Microsoft\Updates\
  3. In the right navigation pane, double-click the UpdateExeVolatile key.
  4. Configure the key with a value of 0
  5. Close Registry Editor.
https://technet.microsoft.com/en-us/library/cc164360(v=exchg.80).aspx


2. Organization Preparation FAILED
Error: 8224
Error:  The following error was generated when "$error.Clear();   install-ExchangeSchema -LdapFileName ($roleInstallPath + "SetupData"+$RoleSchemaPrefix + "schema0.ldf")
" was run: "There was an error while running 'ldifde.exe' to import the schema file 'C:WindowsTempExchangeSetupSetupDataPostWindows2003_schema0.ldf'. The error code is: 8224. More details can be found in the error file: 'C:Usersadministrator.{your-domain}AppDataLocalTemp2ldif.err'".
There was an error while running 'ldifde.exe' to import the schema file 'C:WindowsTempExchangeSetupSetupDataPostWindows2003_schema0.ldf'. The error code is: 8224. More details can be found in the error file: 'C:Usersadministrator.{your-domain}AppDataLocalTemp2ldif.err'

Solution

https://social.technet.microsoft.com/Forums/exchange/en-US/d8713608-1a4d-4d08-b66c-9a38c6bf4625/error-code-8224-ldifde-exchange-2013-installation-failure

Fore Replicate between DCs

https://technet.microsoft.com/en-us/library/cc816926(v=ws.10).aspx

To force replication over a connection

  1. Open Active Directory Sites and Services: On the Start menu, point to Administrative Tools, and then click Active Directory Sites and Services.
  2. In the console tree, expand Sites, and then expand the site to which you want to force replication from the updated server.
  3. Expand the Servers container to display the list of servers that are currently configured for that site.
  4. Expand the server objects and click their NTDS Settings objects to display their connection objects in the details pane. Find a server that has a connection object from the server on which you made the updates.
  5. Click NTDS Settings below the server object. In the details pane, right-click the connection object whose From Server is the domain controller that has the updates that you want to replicate, and then click Replicate Now.
  6. When the Replicate Now message box appears, review the information, and then click OK.


Thursday, September 3, 2015

Powershell to Uninstall Java JRE installed in Windows

Powershell to Uninstall Java JREs any version 7s  from windows.

create a text file which lists workstations or servers - eg. computers.txt

$computers=Get-Content "C:\computers.txt"
Foreach ($computer in $computers)
{
 $java = Get-wmiobject -ComputerName $computer -Filter "name like 'Java%' AND version like '7%'" | % {$_.Uninstall()}
}

Thursday, July 23, 2015

Configuring Outgoing email in SharePoint 2013


(I) Creating Receive Connector in Exchange 2013

1. Go to exchange server and open EAC. Select Mail Flow from the left, choose receive connector and click + click as show below
2. On the Receive Connector page, enter new name for the connector and keep the rest default

3. Under Network Binding, click on pencil to edit 

4. Enter the IP of SharePoint Server and click on Save


5.Click on Finish

6. From the EAC, edit the newly created receive connector, go to Security and check Anonymous users under Permission groups and click Save



(II) Enable Outgoing mail in Document Library

1. Go to SharePoint Server, Open SharePoint 2013 Central Administration and. Under System Systems, click on Configure outgoing e-email settings 


2.On the Outgoing E-Mail Settings, Enter Outbound SMTP server which is your exchange server FQDN, From Address, reply address and click on OK.

3. Now it is time to login the SharePoint Site and go to the document library. Click the library where you want to setup the alert.  we will see Alert me icon as we have setup the outgoing email . Click on the Alert Me and choose Set alert on this library

4. On the New Alert Page, make the selection as per your needs. I kept all as default and click OK.




Once the above is setup properly, you should receive an email confirming the setup.









Configure Incoming emails in SharePoint Server 2013

In couple of months time, I will have to implement SharePoint 2013 at my work. I have started playing around with installation and configuration on my lab environment. I am going to blog any issues that I encountered and the solutions for future reference.

Lab Info:

OS: Windows Server 2012 R2
Database : MS SQL Server 2012 Standard
Active Directory Certificate Service
SharePoint 2013
Exchange 2013
Single Farm will suffice


After I configured incoming emails in both SharePoint and Exchange 2013, I did testing by sending a document but never made it through to SharePoint Document folders.  I am going to document the requirements for SMTP configuration along with the creating send connectors in Exchange.


 Topics:
(I) Installing SMTP  feature in SharePoint Server
(II) Installing certificate for SMTP service
(III) Configure SMTP on SharePoint Server
(IV) Creating Send Connector in Exchange 2013 
(V) Enable Incoming Email on document Library


(I) Installing SMTP  feature in SharePoint Server

1. On the SharePoint server, open Server manager and click on Manage -> Add Roles and Features.
2. Click Next on the following screen

3. Choose "Select a server from the server pool" and click Next


4. Click Next on the Roles Screen, Select Features from the left, check SMTP from the features, click Next


5. Click Add Features, Next and Install

(II) Install Certificate 

As a part of security requirement, SMTP service is required to implement TLS encryption. Under the Properties for the SMTP service, in the Access Tab, the Require TLS encryption check box is grayed out.

I assume that you already have Active Directory Certificate installed on your environment and certificate is installed in Exchange too. We need to request and install certificate in SharePoint/SMTP server.

a. Run MMC
b. From File menu, Choose Add/Remove Snap-in

b. From the Available snap-ins, select Certificate and click on Add

c. Choose Computer Account and click Next


d. Choose Local Computer from select computer and click Finish



e. You should see certificates(local computer) on the selected snap-ins; and click OK.


f. Right Click on personal,->Choose All Tasks-> Click on Request New Certificate


g. On the Certificate Enrollment, click Next


h. under Request Certificates, choose Computer and Click on Enroll


i. On the certificate installation results page, click Finish



h. In the Certificate console of SharePoint server, navigate to Personal, Certificates, the new certificate has been installed.



Now the certificate is made available to the SMTP service, Secure Communication -> Require TLS encryption is available and no more grayed out.



(III) Configure SMTP on SharePoint Server

a. Browse to Server manager -> Local Server->Tools-> "Internet Information Services (IIS) 6.0 manager"

b.Expand Server Name-> Right Click on SMTP and click on Properties

c. On the General Tab,  select Enable logging and keep everything as default.

d. Click on the Access Tab-> Under Secure communication -> check Require TLS Encryption


e. Under Access->click on Authentication and make sure Anonymous is selected


f. Under Access ->Click on connection and make sure All except the list below is selected

g. Under Access-> Select Relay and make sure All except the list below is selected.

h. Select Delivery Tab-> Outbound Security

i. under Outbound Security, make sure Anonymous Access and TLS encryption are selected


j. Delivery Tab->click Advanced

k. Check the SMTP/SharePoint Server FQDN is displayed.




(IV) Creating Send Connector in Exchange 2013 
(V) Enable Incoming Email on document Library



(VI) Configuring AD to allow contracts to show up in the OAB