Verbose status on welcome sceen

It enabled Verbose Status Messages in Windows Vista/7/2008

1. Open regedit
2. "HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\
   CurrentVersion\\Policies\\System"
3. Create DWORD VerboseStatus (or DWORD-32 for 64bit OS)
4. Change Value to 1
5. Reboot

Resest CSC file

1. Open up registry editor (WARNING: Only for Advanced Users)
2. Browse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Csc
3. Add a new key (folder) called Parameters
4. Under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Csc\Parameters, add a new DWORD called FormatDatabase and set its value to 1

Create croj job at VMware Esxi

1. chmod +w /var/spool/cron/crontabs/root
2. vi  /var/spool/cron/crontabs/root
3.  chmod -w /var/spool/cron/crontabs/root
4.  Tambahkan cronjob, misalnya
     20 1 26 11 * shutdown -h now #jam dalam format UTC (beda +7 jam dengan WIB)
5. chmod +w /var/spool/cron/crontabs/root
6. Run the command "cat /var/run/crond.pid"  #catat nomor pid
7. Run the command "kill 12345" where "12345" should be replaced with the number output by the previous command
8. Restart cron "/usr/lib/vmware/busybox/bin/busybox crond"

Setelah reboot conjob akan diremove/lost 

Windows NFS server to Unix nfs client

Force online file

1. Locate and click the following registry subkey: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\NetCache

2. Click Edit, point to New, and then click DWORD Value.
3. Type SilentForcedAutoReconnect, and then press ENTER to name the value.
4. Double-click SilentForcedAutoReconnect.
5. In the Value data box, type 1, and then click OK.

Create new Swap file

The quicker way of getting the same file is by using the fallocate program. This command creates a file of a preallocated size instantly, without actually having to write dummy contents.
We can create a 4 Gigabyte file by typing:

sudo fallocate -l 4G /swapfile

The prompt will be returned to you almost immediately. We can verify that the correct amount of space was reserved by typing:

ls -lh /swapfile

-rw-r--r-- 1 root root 4.0G Apr 28 17:19 /swapfile

As you can see, our file is created with the correct amount of space set aside.

Enabling the Swap File

Right now, our file is created, but our system does not know that this is supposed to be used for swap. We need to tell our system to format this file as swap and then enable it.
Before we do that though, we need to adjust the permissions on our file so that it isn't readable by anyone besides root. Allowing other users to read or write to this file would be a huge security risk. We can lock down the permissions by typing:

sudo chmod 600 /swapfile

Verify that the file has the correct permissions by typing:

ls -lh /swapfile

-rw------- 1 root root 4.0G Apr 28 17:19 /swapfile

As you can see, only the columns for the root user have the read and write flags enabled.
Now that our file is more secure, we can tell our system to set up the swap space by typing:

sudo mkswap /swapfile

Setting up swapspace version 1, size = 4194300 KiB
no label, UUID=e2f1e9cf-c0a9-4ed4-b8ab-714b8a7d6944

Our file is now ready to be used as a swap space. We can enable this by typing:

sudo swapon /swapfile

We can verify that the procedure was successful by checking whether our system reports swap space now:

sudo swapon -s

Filename                Type        Size    Used    Priority
/swapfile               file        4194300 0       -1

We have a new swap file here. We can use the free utility again to corroborate our findings:

free -m

             total       used       free     shared    buffers     cached
Mem:          3953        101       3851          0          5         30
-/+ buffers/cache:         66       3887
Swap:         4095          0       4095

Our swap has been set up successfully and our operating system will begin to use it as necessary.

Make the Swap File Permanent

We have our swap file enabled, but when we reboot, the server will not automatically enable the file. We can change that though by modifying the fstab file.
Edit the file with root privileges in your text editor:

sudo nano /etc/fstab

At the bottom of the file, you need to add a line that will tell the operating system to automatically use the file you created:

/swapfile   none    swap    sw    0   0

Save and close the file when you are finished.

Adding a Hard Drive to Solaris 10 (Copas http://utahsysadmin.com/2008/02/07/adding-a-hard-drive-to-solaris-10)

Here’s how you would add a hard drive to Solaris 10, including the format, fdisk, partition, and then creation of the file system. Of course, you first need to actually add the hard drive physically to the machine, I’m not going to cover that – if you don’t know how to do that then the rest of the information isn’t going to help!
If you installed a drive through VMWare while the VM is running, you will need Solaris to recognize the new drive. In this case, run devfsadm, otherwise boot your system and Solaris should recognize the new drive.
First, here’s the original drives (c0t0d0 & c1t0d0):

# ls /dev/rdsk/*s0
/dev/rdsk/c0t0d0s0 /dev/rdsk/c1t0d0s0

Have Solaris check for new hardware:

# devfsadm

Now you can see there is a new disk on another bus (c1t1d0):

# ls /dev/rdsk/*s0
/dev/rdsk/c0t0d0s0 /dev/rdsk/c1t0d0s0 /dev/rdsk/c1t1d0s0

Next, we want to format the drive (which includes creating the partitions):

# format
Searching for disks…done
AVAILABLE DISK SELECTIONS:
0. c1t0d0
/pci@0,0/pci1000,30@10/sd@0,0
1. c1t1d0
/pci@0,0/pci1000,30@10/sd@1,0
Specify disk (enter its number):

Type “1″, the option for the new drive and hit “enter”. Depending on the type of disk it may be preformatted:

selecting c1t1d0
[disk formatted]

If your drive is not formatted, type format at the format prompt to low level format your hard drive. Next, we need to use fdisk to create the partitions, type “y” to create the default Solaris partition:

format> fdisk
No fdisk table exists. The default partition for the disk is:
a 100% “SOLARIS System” partition
Type “y” to accept the default partition, otherwise type “n” to edit the
partition table.
y

Next enter the partition menu, by typing partition:

format> partition

You can print out the current partitioning first if you like:

partition> print
Current partition table (original):
Total disk cylinders available: 1020 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks
0 unassigned wm 0 0 (0/0/0) 0
1 unassigned wm 0 0 (0/0/0) 0
2 backup wu 0 – 1020 1.99GB (1021/0/0) 4182016
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 unassigned wm 0 0 (0/0/0) 0
7 unassigned wm 0 0 (0/0/0) 0
8 boot wu 0 – 0 2.00MB (1/0/0) 4096
9 unassigned wm 0 0 (0/0/0) 0

In this case, I just want to create one large partition for some extra storage so I will allocate all I can to partition 0. Note that partition 2 is used to reference the entire drive and is not a usable partition. To modify a given partition, just enter the number of the partition at the partition prompt:

partition> 0
Part Tag Flag Cylinders Size Blocks
0 unassigned wm 0 0 (0/0/0) 0
Enter partition id tag[unassigned]:
Enter partition permission flags[wm]:
Enter new starting cyl[0]: 1
Enter partition size[0b, 0c, 1e, 0.00mb, 0.00gb]: 1019c

And now to print the partition table again you can see what has changed:

partition> print
Current partition table (unnamed):
Total disk cylinders available: 1020 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks
0 unassigned wm 1 – 1019 1.99GB (1019/0/0) 4173824
1 unassigned wm 0 0 (0/0/0) 0
2 backup wu 0 – 1020 1.99GB (1021/0/0) 4182016
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 unassigned wm 0 0 (0/0/0) 0
7 unassigned wm 0 0 (0/0/0) 0
8 boot wu 0 – 0 2.00MB (1/0/0) 4096
9 unassigned wm 0 0 (0/0/0) 0

Save your changes by writing the label to the disk:

partition> label
Ready to label disk, continue? y

Quit out of the partition prompt, and then the format prompt, which takes you back to the command prompt:

partition> quit
format> quit
#

Now we are ready to create a file system on this new partition (in this case UFS).

# newfs /dev/rdsk/c1t1d0s0
newfs: construct a new file system /dev/rdsk/c1t1d0s0: (y/n)? y
/dev/rdsk/c1t1d0s0: 4173824 sectors in 1019 cylinders of 128 tracks, 32 sectors
2038.0MB in 45 cyl groups (23 c/g, 46.00MB/g, 11264 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 94272, 188512, 282752, 376992, 471232, 565472, 659712, 753952, 848192,
3298432, 3392672, 3486912, 3581152, 3675392, 3769632, 3863872, 3958112,
4052352, 4146592

Make sure that the file system is clean:

# fsck /dev/rdsk/c1t1d0s0
** /dev/rdsk/c1t1d0s0
** Last Mounted on
** Phase 1 – Check Blocks and Sizes
** Phase 2 – Check Pathnames
** Phase 3a – Check Connectivity
** Phase 3b – Verify Shadows/ACLs
** Phase 4 – Check Reference Counts
** Phase 5 – Check Cylinder Groups
2 files, 9 used, 2020758 free (14 frags, 252593 blocks, 0.0% fragmentation)

Next, add the proper line to /etc/vfstab:

/dev/dsk/c1t1d0s0 /dev/rdsk/c1t1d0s0 /data ufs 2 yes -

And then mount the partition. In this case, I’m making a /data partition:

# mkdir /data
# mount /data
# df -h /data
Filesystem size used avail capacity Mounted on
/dev/dsk/c1t1d0s0 1.9G 2.0M 1.9G 1% /data

Change Harddisk Poweredge3310 with Sun Solaris Running

1. check with cfgadm -al
    Find the label AP-ID  that the disk will be replace
2. Unconfigure the hard disk that will be replace
#cfgadm -c unconfigure c1::dsk/c1t1d0
3. verify that the disk is now unconfigured
#cfgadm -al
4. Replace the disk
5. Connect the new drive
#cfgadm -c configure c1::dsk/c1t1d0
6.  format the disk and label the disk
#format > type > label
7.  Run metastat then check the disk that needed maintenance
8. Run metareplace -e d8 c1t1d0s0 (that the disk need maintenance)

done

OpenKM 5.1.9 with PostgreSQL 9.3.7

Step:
1. ubuntu 14.04
2. Postgresql9.3.7 > sudo apt-get install postgresql-9.3
3. install jdbc Driver > sudo apt-get install libpostgresql-jdbc-java
4. install Openkm 5.1.9
5. copy file postgresql-jdbc4-9.2.jar > cp /usr/share/java/postgresql-jdbc4-9.2.jar $JBOSS_HOME/server/default/lib/
6 follow this link http://wiki.openkm.com/index.php/PostgreSQL_-_OpenKM_5.0
note: don't forget to create database

Remote Desktop Licensing Error

Today I got a call from client that he can’t connect to his Remote Desktop Service  from his Windows 7 client.

He would get following error: The remote computer disconnected the session because of an error in the licensing protocol. Please try connecting to the remote computer again or contact your server administrator.

Since I was sure the licensing was in order I searched for another possible problems.

The cause of the problem was in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing.

So here is one of possible solutions if you are getting this error when trying to connect to Terminal Server (Be sure to backup your registry before you do this or export the MSLicensing keys, in case this isn’t the cause of your problems):

1. Open registry editor (Start > Run > regedit)
2. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ and find MSLicensing folder
3. Right click on it and select delete
4. Start Remote Desktop Client (Start>Run>mstsc) as local administrator to rebuild the deleted keys

Getting an Exchange Database into a Clean Shutdown State using Eseutil

1. Check to see if your database is in a Clean State by running the following command in EMS:
Eseutil /mh "path/to/the/database.edb"

2. If it is in a clean state, simply copy all the .log files out of the exchange database directory to any location and mount the database.

So you’ve just restored an Exchange database, and now you are trying to mount it. To your surprise, you are getting an error similar to the following:

Couldn’t mount the database that you specified. Specified database: DB2; Errorcode: An Active Manager operation failed. Error: The database action failed. Error: An error occurred while trying to select a database copy for possible activation. Error: The database ‘DB2′ was not mounted because errors occurred either while validating database copies for possible activation, or while attempting to activate another copy. Detailed error(s):
An Active Manager operation failed. Error: Operation failed with message: MapiExceptionCallFailed: Unable to mount database. (hr=0×80004005, ec=-550)

Before you can mount a database restored from a backup, it needs to be in a clean shutdown state. You can use the Eseutil tool to check whether a database is in a clean shutdown state – if it is not in a clean shutdown state you can perform a repair to get the database into consistency.

Soft Recovery using Eseutil

The first thing you want to do is verify that the database is in a dirty shutdown state. We can do this using the eseutil /mh command. For example:

The output from the above command shows us that the database is dirty shutdown:

We can also see from the output, under Log Required, the database is missing a transaction log. We can replay log files into the database (as long as they exist) to get the database into consistency. To do this, we use the following syntax with eseutil:
eseutil /r /l /d
For example, my log file prefix is E02, and my database and logs are stored in G:\E_\Program Files\Microsoft\Exchange Server\V14\Mailbox\DAGDB1 . Here is a screen shot of the command:

When this repair is complete, I can run the eseutil /mh command again to verify that the database is in a clean shut down state:

At this point, I’ll be able to mount the database. This will almost always work when you restore a database from a Windows Server Backup, but there may be times when this doesn’t work and you need to perform a hard repair.

Performing a Hard Repair

Performing a hard repair using eseutil /p will check the database for any damaged pages; if it finds any, it will delete them. Make sure that you can live without any data inside the database before doing a hard repair, because you may lose data. Also, make sure you have twice as much free space as the size of the database before doing a hard repair – this is required for the temporary database that will be created.
To perform a hard repair, use the eseutil /p command, as shown here:

Once this completes, you can use the eseutil /mh command to verify the database is clean shutdown.

Redirection Folder My document From GPO

The following instructions work for redirecting My Documents/Documents. I cannot guarantee it will work for other redirected folders but it follows the same pattern so there is no reason why it shouldn't.

When setting up the root folder for redirected folders:

Setting the NTFS permissions

Create the folder in the required location (ie. E:\Users)

Disable inheritance of permissions from the parent and remove all inherited permissions by clicking the appropriate button.

One entry will already be in the DACL: Local Administrators.

1. Alter Local Administrators: Full Control: This folder, subfolders and files
2. Add SYSTEM: Full Control: This folder, subfolder and files.
3. Add CREATOR OWNER: Full Control: This folder, subfolders and files.
4. Add Authenticated Users: List folder / read data, Create folders / append data: This folder only
5. Add Domain Admins: Full Control: This folder, subfolders and files.
6. Click OK.

These permissions grant users the ability to create their redirected folder in the root folder but not the ability to browse the contents of other people's folders. Best practice dictates that you should allow the redirected folder locations to create themselves as users log on.

Create the share and add share permissions

Share the root folder created earlier as \\SERVER\Users (or if you want to hide it, \\SERVER\Users$\

Adjust the share permissions as follows:

1. Remove Everyone
2. Grant Authenticated Users Full Control
3. Grant Domain Admins Full Control (Not necessary but useful for completeness)

Configure the GPO

1. Open Group Policy Manager
2. Create a new GPO or edit your existing one.
3. Expand User Configuration > Policies > Windows Settings > Folder Redirection
4. Right-click My Documents/Documents and click Properties.
5. Choose Basic - Redirect everyone's folder to the same location
6. Under Target folder location choose Create a folder for each user under the root path
7. Set the Root Path: to \\SERVER\Users
8. As you type, you will see an example location listed to show you how the folders will be created as users log on.
9. On the Settings tab, uncheck Grant the user exclusive rights to Documents
10. Under Policy Removal, select your preferred option depending on your requirements.
11. Link the GPO at the appropriate OU.

Despite assurances from Microsoft in another article, granting users exclusive rights to My Documents in the GPO will stop you from being able to access the contents of a users' folder. Probably not good for backup!

Configuring HP-UX 11i for the HP LeftHand SAN

Follow these steps to configure the iSCSI initiator, incl

uded in the installation of HP-UX 11i, to use with

the HP LeftHand SAN.

Step 1: Verify the iSCSI initiator is running

•

To verify that the iSCSI initiator is running

, in HP-UX 11i execute the following command:

iscsiutil –l

This returns something similar to the following:

Initiator Name :

iqn.1986-03.com.hp:hpntc916.Z3e113981e2afd927

Initiator Alias :

Authentication Method :

CHAP Method : CHAP_UNI

Initiator CHAP Name :

CHAP Secret :

NAS Hostname :

NAS Secret :

Radius Server Hostname :

Header Digest : None,CRC32C (default)

Data Digest : None,CRC32C (default)

SLP Scope list for iSLPD :

Use the initiator node name (shown here in bold) to register the server in the CMC as detailed

in the

HP SAN/iQ Software Users Guide

.

Step 2: Add the discovery target address

•

To add the discovery target address or addresses,

run the following command using the virtual IP

(VIP) address in the cluster:

iscsiutil –a –I (Virtual IP)

(Note that there is no confirmation output of this command.)

2

Step 3: Confirm connection to volume targets

•

Run the following command to ensu

re that the initiator was able to establish a connection to

the volume targets:

iscsiutil –p –D

This returns discovery target informatio

n, which looks similar to the following:

Discovery Target Information

----------------------------

Target # 1

-----------

IP Address : 10.160.32.21

iSCSI TCP Port : 3260

iSCSI Portal Group Tag : 1

User Configured:

----------------

Authentication Method :

CHAP Method : CHAP_UNI

Initiator CHAP Name :

CHAP Secret :

Header Digest : None,CRC32C (default)

Data Digest : None,CRC32C (default)

 In this example, there are 1 volumes.

Note:

The iSCSI sessions were not configured us

ing CHAP, SLP, or any form of digest.

For information on these options, use the

HP SAN/iQ Software Users Guide

and the

iscsiutil

man pages.
Step 4: Confirm HP SAN/iQ

Software volumes

•

To confirm that HP-UX has operating HP SAN/iQ

Software volumes, and to discover the logical

device files for the targets,

enter the following command:

ioscan –fnH 255

This command returns something similar to the following:

Class I H/W Path Driver S/W State H/W Type Description

===========================================================================

ext_bus 21 255/0/3.0 iscsial CLAIMED INTERFACE iSCSI-SCSI

Protocol Interface

disk 1032 255/0/3.0.0.0 sdisk CLAIMED DEVICE

LEFTHANDiSCSIDisk

/dev/dsk/c21t0d0 /dev/rdsk/c21t0d0

ext_bus 22 255/0/6.0 iscsial CLAIMED INTERFACE iSCSI-SCSI

Protocol Interface

disk 1033 255/0/6.0.0.0 sdisk CLAIMED DEVICE

LEFTHANDiSCSIDisk

/dev/dsk/c22t0d0 /dev/rdsk/c22t0d0

ext_bus 24 255/0/12.0 iscsial CLAIMED INTERFACE iSCSI-SCSI

Protocol Interface

disk 1035 255/0/12.0.0.0 sdisk CLAIMED DEVICE

LEFTHANDiSCSIDisk

/dev/dsk/c24t0d0 /dev/rdsk/c24t0d0

There is an entry for each target or volume.

Note:

HP-UX has a limit of 256 block device targets. Af

ter the initial discovery, HP-UX creates a single

logical device for each new device

target (volumes and snapshots) it finds on the HP LeftHand SAN.

Once the HP-UX iSCSI initiator recognizes a target, yo

u need to clear devices from the kernel registry.

See “

Clearing the kernel registry

” below for details of the procedure to clear devices from the kernel

registry.

Step 5: Start using the iSCSI volumes

•

You can now begin using the iSCSI volumes as you

would any direct-attached disks, either as raw

disks or by formatting the disks.

Clearing the kernel registry

HP-UX accommodates 256 iSCSI sessions and does

not clear block device links to old targets

including deleted snapshots. You must manually clear the registry of stale sessions once this

maximum is reached in order to

establish new iSCSI sessions. Note that clearing the kernel

registry clears out all configurations, so afte

r clearing you will need to recreate any old

configurations you want to preserve.

Here is the procedure to clear out your iSCSI configuration from the kernel registry:

1.

Before deleting all the iSCSI information in the registry and rebooting the system, preserve

the original configuration as follows:

# ioscan -kfn > /tmp/ioscan.pre_shutdown.out

# iscsiutil -p > /tmp/iscsi_tgt.pre_shutdown.out 

2.

Delete all iSCSI information from the registry (all steps must be done as root):

# echo "iscsi_krs_delete/W 1" |adb -w /stand/vmunix /dev/kmem

(assuming system was booted

from /stand/vmunix ...)

# iscsiutil –x

3.

Reboot the system immediately.

4.

Once the system is back online, you will have

to recreate your iSCSI configuration.

This completes the procedure for configuring HP-UX 11i for use with the HP L

Delete file older then X days

1. Copy file older than X day to destination folder
     > robocopy (Source) (Destination) /move /minage:x
        example: robocopy c:\temp c:\delete /move /minage:7
        copy file older than 7 days form c:\temp to c:\delete
2. Delete all file at c:\delete
    > del /q destination
       example: del /q c:/delete
       
regards, Asnan

Perintah2 Yang sering Digunakan DI EXchange shell

1. Get-Mailboxstatistic | Sort-Object TotalItemSize –Descending

Event ID : 4001 A transient failure has occurred. The problem may resolve itself in awhile. The service will retry in 56 seconds.

1. Check out the database where is the location of Microsoft System Attendant; Use the below command;
Get-MailboxStatistics | Where-Object {$_.DisplayName -eq "Microsoft System Attendant"} | fl
2. Make sure the database is mounted.
*for my lovely Chubby*

Error updating public folder with free/busy information on virtual machine EOBMAIL02. The error number is 0x80004005. On exchange 2007

In the Exchange Management Shell, run the following command: get-publicfolder -Identity "\NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY" -Recurse | fl name,Replicas Notice that at least one of the SCHEDUE+ FREE BUSY folders is missing an Exchange 2010 or Exchange 2007 server listed as a replica. For example, the output may appear as follows: Name : EX:/o=contoso/ou=Exchange Administrative Group (FYDIBOHF23SPDLT) Replicas : {} In the Exchange Management Shell, run the following command: set-publicfolder -Identity "\NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY\" -replicas "" For example, type: Set-publicfolder –identity "\NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY\EX:/o=contoso/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)” –Replicas “Server\Storage Group\Public Folder Database” Verify that the public folder group now has a replica using the command from step 1. In the following example, the folder now has a replica object. Name : EX:/o=contoso/ou=Exchange Administrative Group (FYDIBOHF23SPDLT) Replicas : {Public Folder Database}

Some users cannot access Exchange Server 2007 OWA

To resolve this problem, follow these steps:

1. Open Active Directory Users and Computers.
2. Click View, and then click Advanced Features.

Note To make the Security tab available at both the user level and the organizational unit level, you must enable the Advanced Features option in Active Directory Users and Computers. This option is available under the View menu.
3. Open the properties for both the user level and the organizational unit level that the users are located in, and then locate the Security tab.
4. Click Advanced.
5. Make sure that the following check box is selected:
Allow inheritable permissions from the parent to propagate to this object and all child objects. Include these with entries explicitly defined here.
6. Force Active Directory replication.

stop recovery document at libreoffice

To stop the recovery process, you can delete the file Documents and settings//Application data/Openoffice.org2/user/registry/data/org/openoffice/Office/Recovery.xcu.

Beware, it resets the settings for Autosave in the Tools>Options>Load/Save>General dialog

Renew Self Certificate for Exchange 2007

Dari exchange management shell;


[PS] C:\Windows\system32>Get-ExchangeCertificate -thumbprint "D5AD872B9DF0428478
051463929E85573FF8A4E8" | New-ExchangeCertificate

Confirm
Overwrite existing default SMTP certificate,
'D5AD872B9DF0428478051463929E85573FF8A4E8' (expires 5/31/2012 10:33:18 AM),
with certificate 'D02FA4CB9596FC240B3583811A8A517E76FC2780' (expires 3/12/2017
1:34:12 PM)?
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help
(default is "Y")

dan untuk meng-enable kan iis nya

Enable-ExchangeCertificate -thumbprint “D02FA4CB9596FC240B3583811A8A517E76FC2780” -services IIS

 Remove-ExchangeCertificate –Thumbprint "D5AD872B9DF0428478051463929E85573FF8A4E8"