Posts

Showing posts from August, 2013

How to Move or Copy an SSL Certificate from one Server to Another

Do you have multiple servers that need to use the same SSL certificate? This is very common in an environment where a load-balancer is used to share the load of a website across several different servers. This is also becoming more common as wildcard certificates and UC SSL certificates increase in popularity because they enable a single certificate to work on multiple different domains or subdomains using SSL Host Headers.
What about when you set up a new server or switch hosting companies? How do you move the current SSL certificate to the new server? What if you need to move it to a different type of server? The answers to all of those questions are contained in the following pages. Essentially, you will export SSL certificates from the server that they are currently installed on, move SSL certificates to the new server, and then import SSL certificates on the new server.
Keep in mind that many certificate authorities, require that you purchase a "server lice…

This Task Sequence cannot be run because the program files for cannot be located on a distribution point

Image
Running Task sequence using SCCM 2007 R3 you are receiving this error message:
This Task Sequence cannot be run because the programfiles for cannot be located on a distribution point





Analyzing in WINPE local workstation log file x:\windows\temp\smstslog\smsts.log shows following:


It is clear that the problem is with TST00003.

To find which Package is associated with this number, go to Package Status. On the right pane all packages are shown  with their Package ID. In our case is KB977384 - Advanced Client hotfix where Distribution point is not installed.

To resolve this issue just add New Distribution point to this Package or delete the distribution point and recreate a new one will resolve the issue. Reference : http://tompopov.blogspot.in/2012/12/this-task-sequence-cannot-be-run.html

Rearm the Office 2013 installation

Image
There is a 25-day grace period from the time of installation of Key Management Service (KMS) clients before notifications to activate are displayed to the user. If you want to deploy an image, you must rearm your Office 2013 installation before you capture the image. If you do not rearm, users see notification dialog boxes at the time that the image is deployed, instead of 25 days after deployment. The 25-day grace period gives ample time for a KMS host to be found and activation to succeed. If activation is successful, users do not see notifications to activate.
Rearm the Office installation Rearming does the following important tasks:
Resets the grace timer to 30 days.
Freezes the grace timer until either an Office application is run, or the ospp.vbs script is run.
Resets the client computer ID (CMID). This is important because the KMS host uses the CMID to determine the number of unique clients. To check the CMID, use the command…

Using KMS Manually to Activate Software

This page is intended for technical support providers and network administrators. If you're not one of those, you should talk to your TSP or net admin before proceeding. The concept behind the procedure on this page is explained on our main KMS page.
This page describes how to manually activate products. With this method, you'll need to run commands on each machine - and for each software package - during the 30 day grace period after installation. If you are using virtual machines for testing and cross-compatibility on Macintosh computers, you'll need to use the manual method in those circumstances.
To use this method, first install the software (Windows or Microsoft Office). As part of that process you'll be informed that you have 30 days to activate the product. Complete the steps below during that 30-day period.
This method assumes that Windows or Office has never been activated on this machine before. If your machine had previously been activated wit…

How to setup Microsoft Office 2013 KMS Host on Windows Server 2008 R2

Image
Overview: The KMS Host installation and activation process for Microsoft Office 2013 is similar to the one for Microsoft Office 2010.
Prerequisites: Installation of the update that adds support for Windows 8 and Windows Server 2012 to Windows Server 2008, Windows 7, and Windows Server 2008 R2 KMS hosts is required for a successful installation of the KMS Host.  The update can be downloaded from the link http://support.microsoft.com/kb/2757817.
Installation: STEP 1: If you have not downloaded and installed the update to add support for Windows 8 and Windows Server 2012 to Windows 2008 R2 KMS host, please do so by accessing the link http://support.microsoft.com/kb/2757817 and downloading and installing the appropriate update.
STEP 2: Download the Microsoft Office 2013 Volume License Pack from the Microsoft Download Center (MSDL) site
STEP 3: Double-click the downloaded EXE to run it:
STEP 4: Click Yes on the "Would you like to enter a Microsoft Office 2013 KMS host product…

How to check the activation type and status of Office 2010 and 2013 installations

Image
Use the following steps to see detailed information about what type of activation your Office 2010 and 2013 installation us using and what the status of your activation is.
Open an administrative level command prompt. Navigate to the Office14,15 folder: 32bit Office on 64bit OS – “cd \Program Files(x86)\Microsoft Office\Office14” 32bit Office on 32bit OS and 64bit Office on 64bit OS – “cd \Program Files\Microsoft Office\Office14” Execute “cscript ospp.vbs /dstatus” Look at “LICENSE NAME” for license type and “LICENSE STATUS” for activation status If Office is KMS activated you will see “KMS_Client edition” in the license name field:

If Office is MAK activated you will see “MAK edition” in the license name field:

If Office is Retail activated you will see “Retail edition” in the license name field:













ConfigMgr 2012 console in read-only mode?

Image
After installing a primary under a central admin site you may get the following message when attempting to open the console at the primary site level:  "Your Configuration Manager console is in read-only mode while this site completes tasks related to maintenance mode". This usually indicates that the initial replication between the CAS and the primary isn’t complete yet.  Monitor rcmctrl.log on the CAS and also the Database Replication view in the Monitoring workspace on the CAS.  Once the link state says ‘Link is active’ for the child sites then the replication should be complete and you should be able to open the console at the primary without getting the read-only message.  Also note that this replication may take some time.  My environment took at least an hour to complete.