Welcome, Guest
You have to register before you can post on our site.



Search Forums

(Advanced Search)

Forum Statistics
» Members: 357
» Latest member: Drop Ceiling
» Forum threads: 7,283
» Forum posts: 6,224

Full Statistics

Online Users
There are currently 54 online users.
» 0 Member(s) | 54 Guest(s)

Latest Threads
Goal for Mosley: Join Lew...
Forum: General Discussion
Last Post: linlybest
02-09-2018, 07:05 AM
» Replies: 0
» Views: 599
Ravens begin exploring QB...
Forum: General Discussion
Last Post: linlybest
02-09-2018, 06:50 AM
» Replies: 0
» Views: 212
Will owner Steve Bisciott...
Forum: General Discussion
Last Post: linlybest
02-09-2018, 06:30 AM
» Replies: 0
» Views: 200
Todd Gurley Wins NFL Offe...
Forum: General Discussion
Last Post: aliciahuang
02-07-2018, 06:19 AM
» Replies: 0
» Views: 237
an Imperfect Super Bowl M...
Forum: General Discussion
Last Post: aliciahuang
02-07-2018, 05:57 AM
» Replies: 0
» Views: 169
NHL Power Rankings 2018: ...
Forum: General Discussion
Last Post: aliciahuang
02-06-2018, 06:06 AM
» Replies: 0
» Views: 232
Forum: General Discussion
Last Post: aliciahuang
02-06-2018, 05:46 AM
» Replies: 0
» Views: 226
Dolphins hire Tony Oden a...
Forum: General Discussion
Last Post: aliciahuang
02-05-2018, 07:54 AM
» Replies: 0
» Views: 265
The Patriots' dynasty was...
Forum: General Discussion
Last Post: aliciahuang
02-05-2018, 07:34 AM
» Replies: 0
» Views: 198
Wie konvertiere ich EDB-D...
Forum: General Discussion
Last Post: Wandasallazars
02-02-2018, 10:52 AM
» Replies: 0
» Views: 324

  How to Enable circular logging in Exchange 2010
Posted by: rajeev - 08-24-2017, 10:37 AM - Forum: MS Exchange Server - No Replies

Enabling Circular logging might become essential when you are not using a Backup Exec or backup software which truncate transaction logs automatically. If transaction logs are not getting truncated, these will take huge space on the disk. Enabling circular logging will clear transaction logs automatically. Let us see how you can enable Circular logging on Exchange 2010

Open EMC
Browse to Organization configuration > Mailbox.
Right click Database to which you want to enable circular logging and click on properties.
Click on Maintenance tab and check box "Enable Circular Logging". Click Apply Ok and exit.
Not finished yet. You have to Dismount and then Mount database to effect the changes.

You can also use command shell to do this:

Set-MailboxDatabase -CircularloggingEnabled:$true

Please must see this article prior to making a move to Enable Circular Logging which states Why not to Enable Circular Logging

Print this item

  Petya Ransomware Emerged
Posted by: rajeev - 07-03-2017, 11:08 AM - Forum: Networking and Security - No Replies

Following the recent WannaCry ransomware attack, a new variant leveraging Petya ransomware emerged globally on Tuesday, June 27, 2017 starting in the Ukraine and spreading to millions of potentially affected people around the world. Machines which are up-to-date with Microsoft updates and security patches has a low probability of exposure. Unfortunately, this attack includes the ability to leverage one vulnerable machine on a network and propagate to other machines that were actually current. This has been reported second major ransomware attack in two months.

The malicious software will reach to machine through attachment or from melicious websites. The ransomware infects computers and then waits for about an hour before rebooting the machine. Thereafter it will started encrypting files on the computer. The ransomware takes over machine and will demands $300 as ransom. This ransom is paid in Bitcoins. This is not clear yet who is behind it, but thinkers assume someone who wanted the malware to look like ransomware. It is also guessed that the motive of this attack is destructive against Ukrainian Government. Security researcher Nicholas Weaver told cybersecurity blog Krebs on Security that ‘Petya’ was a “deliberate, malicious, destructive attack or perhaps a test disguised as ransomware”. Pseudonymous security researcher Grugq noted that the real Petya “was a criminal enterprise for making money,” but that the new version “is definitely not designed to make money.

This is designed to spread fast and cause damage, with a plausibly deniable cover of ‘ransomware'. The payment mechanism in the malware was inept to the point of uselessness because it has a single hard coded payment address, meaning the money can be traced. The requirement to email proof of payment to a webmail provider, meaning that the email address can be – and was – disabled; and the requirement to send an infected machine’s 60-character, case sensitive “personal identification key” from a computer which can’t even copy-and-paste, all combine to mean that “this payment pipeline was possibly the worst of all options (sort of ‘send a personal cheque to: Petya Payments, PO Box … ’)”

Almost after one hour of infection Petya will reboot the computer. If you observe that you computer is infected, turn it off completely; Disconnect from Internet. Don't think of paying ransome because the contact details provided may or may not be correct. Format your hard disk and reinstall operating system. Restore your files from backup.

Make sure you have genuine windows and all updates installed including all Microsoft security patches. Ensure good anti virus or Malware protection software is installed. Keep a good backup of important data. Don't open attachment from unknown source. Understand well that nothing on internet is free now-a-days; everything comes packaged with something. Stay protected !!!!

All information above is based on web search and online authentic technical channels. Verify your self before acting in any way.

Print this item

  There are no Remote Desktop License Servers available to provide a license
Posted by: gotzuadmin - 02-22-2017, 07:44 AM - Forum: Windows Administration - No Replies

Its windows server 2012 and you are trying RDP to it but getting kicked out with error "there are no Remote Desktop License Servers available to provide a license .. "

First please ensure that you have configured your terminal service fine. Open gpedit.exe and browse to Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Licensing
You will see three keys there but your focus is only "Set the Remote Desktop licensing mode". Enable this and set License mode Per User but you can change to Per Device if your CALs are like that.
Some people will like to define terminal server name/IP by enabling "Use the specified RD license servers" Though this may not be a mandatory option but you can do if it is required.
Force removing of grace period key from if you had Trial RDS enabled and are expired. Removing that registry key is not as simple like cleaning other registry keys. Here is How to force cleanup grace period registry key .

Verify that RDS licensing server is configured fine. Load Server Manager and goto RD services/Overview / Deployment properties. Click on RD Licensing and use Per user or Per Device as per purchased CALs.
Finally from Administrative Tools open Terminal server License manager and add your CALS and install.

You shall be good to go. Please comment if you have any questions or suggestions.

Print this item

  How to extend terminal server trial license
Posted by: gotzuadmin - 02-22-2017, 07:19 AM - Forum: Windows Administration - No Replies

The terminal trial license period is for 120 days. What if you are still undecided to buy licenses but want terminal server trial license to be extended for another term. Though this is an easy by deleting  l$rtmtimebomb registry key under Grace Period. It looks so simple but no matter if you are logged in as administrator account, you will not be able delete saying permission denied. Taking ownership or elevating rights will not work either.
Here comes to PsExec Tool will be your savior here. How to use it? Follow below simple steps and you will be good to go:

Download Sysinternal Suite from Technet.
Extract the compressed folder. Now you will be see many utilities including PsExec and PsExec64. If your Terminal server is 64 bit then use PsExec64. The syntex is as below:

psexec64 -s -i regedit.exe

This load registry with supreme elevated rights. Browse to below registry and delete   l$rtmtimebomb key

HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod

Deleting this key will get you activate terminal trial licenses on your server
Deleting a registry may cause your server to crash or stop responding so make sure to export settings before deleting any registry and you should have complete backup of your server and capability to restore from backup
Any suggestion and comment is much appreciated.

Print this item

  Offsite backup module you are using
Posted by: gotzuadmin - 02-03-2017, 10:47 AM - Forum: Backup and Disaster Recovery - No Replies

What Offsite backup module you are using in your network.

Also specify if own cloud storage is supported.


Print this item

  Install and Configure VM ware ESXi 4.1 host
Posted by: gotzuadmin - 01-29-2017, 04:20 PM - Forum: VMware - No Replies

As it was stated in previous post that ESXi 4.1 software has a footprint as small as 70 mb, just like firmware insalled on the system. It comes as embedded in a server's physical hardware by vendor or burnt onto an external USB key. But remember that moving ESXi embedded on USB external key from one server to another is not supported. The ESXi software also comes as an installable CD/DVD.

Let's now proceed with the installation. We are considering Dell server which meets all pre-rquisits, hardware requirements etc. and we are installing from a DVD. To know more about hardware requirements please visit below link: http://kb.vmware.com/kb/1022101

Turn on the server, insert the DVD and boot from disk. Once installation is initiated, it will take few minutes to complete without any further keyboard inputs and you will be presented with following screen after installation is complete.

Next step is to configure your ESXi 4.1 host. Press F2 to go to configuration screen. You will be prompted for user name password. By default admin user is 'root' and password is blank. Once you login you will reach to configuration console know as (DCUI) Direct Console User Interface. The DCUI looks as below:
First thing is to configure root password. It is important to configure root password to be able to login to vSphere client. 

-Configure Host Name
-Configure IP Address, Subnet mask, Gateway
-Configure DNS servers.

Once above configuration is done, press F2 to exit the DCUI and F12 to reboot your host. Make sure you add a host record to your DNS server for this ESXi host. Now you are ready to create virtual machines on your ESXi 4.1 host. Open browser on any machine in the same subnet in which you have your host. Type the host name or IP address of your ESXi 4.1 host and you will be presented with below screen:

Click Download vSphere Client, once download completes continue with the istallation. Once installation is complete launch vSphere client from Start > All programmes >> enter the IP address or Host Name of your ESXi 4.1 host >> user name - root and password.

You are now in virtualisation world, explore all settings and my next post will be about creating virtual machines.

Print this item

  VMware vSphere Disk Provisioning for a Virtual Machine
Posted by: gotzuadmin - 01-29-2017, 04:17 PM - Forum: VMware - No Replies

VMware vSphere Disk Provisioning for a Virtual Machine

There are two type of provisioning; Thin and Thick but in production Thick is widely practiced. Thick provisioned disk takes entire allocated space and give better performance. Though thin provisioned disk does not require entire allocated space immediately but if you have more number of thin provisioned disks in your vSphere environment, high chances are that datastore will run out of disk space. More over performance too is lower in thin provisioned disk as compared to thick provisioned disk.

Apart from provisioning disks you will have to be careful in selecting type of Virtual disk; i.e. Independent disk or non-Independent. First and far-most Independent disks are non-snapshot supportive. That means if you create an Independent disk you have further two options to select which are Persistent or Nonpersistent.

If you select an Independent disk in Persistent mode that means data is written to disk permanently.

If you select an Independent disk in Nonpersistent mode that means data written to disk is not permanent. The Virtual machine will loose all changes when it is rebooted. 

Print this item

  vSphere esxi 6.0 few new features added
Posted by: gotzuadmin - 01-29-2017, 04:15 PM - Forum: VMware - No Replies

-ESXi 6.0 support VM Virtual Hardware Version 11.

-Few other enhancements are support for 128 vCPUs, 128 TB RAM, Hot-Add RAM to vNUMA, WDDM 1.1 GDI Acceleration.
-Maximum virtual disk size now is 64 TB.
-The USB 3.0 xHCI Controller is upgraded to xHCI controller version 1.0. It supports both USB 3.0 and 2.0. Total 8 reserved ports; 4 for USB 3.0 and 4 for 2.0.
-VMXNET3 Driver is upgraded to Large Reciev offload. This is a hardware offload technique which help reduce CPU cost for network packet processing by aggregating multiple incoming transmission control protocole or TCP/IP packets into one single packet.
-Each VM can support upto 32 serial ports.
-Serial and parallel ports can now be removed from a virtual machine when using compatibility 6 (vHW 11).
-The HDFS driver has been enhanced to reduce the number of reboots required when installing VMware Tools.

Print this item

  The VMRC console has disconnected attempting to reconnect
Posted by: gotzuadmin - 01-29-2017, 04:13 PM - Forum: VMware - No Replies

Recently I am experiencing problem seeing console of VM through vCentre Vsphere 5.0. When I click on console of any vm it show below error:
The VMRC console has disconnected attempting to reconnect..

To resolve this I have tried few steps as below:

1. Rebooted the host.
2. Migrated VM to another host.
3 Rebooted the VMs

I have two hosts and each has couple of VMs. Console of every VM and under both host give above error. 

Thank You 

Print this item

  How to create iSCSI target on windows server 2008 R2 for ESXi host
Posted by: gotzuadmin - 01-29-2017, 04:12 PM - Forum: VMware - No Replies

http://www.microsoft.com/en-in/download/...x?id=19867 . Once installed launch Microsoft iSCSI software target and configure it as below:
1. In Microsoft iSCSI console Right click on iSCSI targets and click 'Create iSCSI target'.
2. Click next.
3. Name the target and click next.
4. Under IQN identifier tab add the the WWN name of your ESXi host if it is not listing upon clicking browse. You can get it by login to your ESXi host from vSphere client > click Storage adapter > iSCSI software adaptor. 
5. Click next and finish.
6. Now we have to create a disk and assign it to this iSCSI target. 
7. Right click Devices in Microsoft iSCSI console. Click create virtual disk and click next.
8. Browse to the location to save this vhd and name with extention as yourVHD.vhd.
9. Click Next and allocate the size in MBs. Click next
10. click Add and select the iSCSI target created at steps 1 to 5 above. 
11. Click next and finish.
12. Click to select Devices > right click the yourvhd.vhd > disk access and click mount read/write.
13. Now our LUN is ready to be presented and discoverable by vmware ESXi host.

Now addin this LUN to our vmware esxi host.
1. Login to esxi host from vSphere client.
2. Go to Configuration>storage adapter 
3. Click vmhba33 under iSCSI software adapter and click propeties.
4. Under general tab click configure and enable.
5. Click static discovery > click add and type IP address of iSCSI server > iSCSI target name. Click OK
6. Click scan All and the iSCSI softwer adapter will display the LUN.
7. Now go to Storage and click rescan all. Select the discovered LUN and click Add Storage > select disk/LUN and click next name the datastore > click next finish.
8. You have the new Datastore available for hosting VMs.

Please share your valuable suggestions and feed back. 

Print this item