X

Rochester, MN Web Site Designer

Shawn Hyde has been developing and marketing creative custom websites for just over 13 years. If you're looking for a unique and creative website or effective internet marketing strategy, I would be happy to help you out.

You can contact me via my Contact Form or by phone at 507 536-9557.

Connect with Shawn Hyde on these Social Networks:

X
Moskowitz, LLP
Homes 2 Enjoy
KRPR Radio
Hawaiian Island Chocolates
Happy Smile Pediatric Dentistry
DejaFX
11 Charlie
Area51
Area51 (Pre 2010)
Corinthian Dental
Fusion Zero
GHU
issak-ibrahim
Pethumb
Siniia Foods
Pricewatch
Pricewatch (Mug, 3D Render)
X

Shawn Hyde ∙ Blog Feed

VPN setup for Windows Server 2012, How to:

VPN Server Setup in Windows Server 2012

 

Simple walkthrough of the steps you need in order to accomplish this are as follows:

  • Open Server Manager > Add roles and features > Next > Choose (default) role based or feature based > Next
    • Select the server you would like to install VPN services to > Next
    • Select Remote Access Role > Add features > Next > Next > Next
    • Choose (Default) DirectAccess and VPN (RAS) > Next > Next > Next > Install > Close
  • In Server Manager select Remote Access > Select more on the right of the configuration notice or select from you pending tasks
    • Select open getting started wizard if you choose the first method.
    • Select Deploy VPN Only
    • Once the Routing and Remote Access MMC is up right click the Server and choose "Configure and Enable Routing and Remote Access". > Next
      • Select Custom > Next > VPN Access > Finish > OK > Start Service
    • right click server and choose properties
      • Select IPV4 tab to configure IP Pool or leave it Dynamic
  • From Computer management or Active directory you will need to create a group or modify each user you would like to have access to the VPN
    • right click user > properties > dial-in tab > allow access > apply > ok

You should also properly setup you VPN security if you have any critical data being transmitted via this network. For assistance with this you can contact a professional IT company like Area51.mn to assist you with proper setup and network security.  

Microsoft Exchange RPC Client Access fails due to high memory usage in Microsoft® SharePoint® Search Component (aka noderunner.exe) on Exchange 2013

After installing exchange 2013 and migrating clients over to the server you may notice Microsoft® SharePoint® Search Component or noderunner.exe running multiple instances with high memory usage. This is because Microsoft has integrated parts of sharepoint into exchange 2013. This process runs when accounts are first migrated and periodically to index email data stores for OWA in order to make search results fast, very fast.

You can disable Microsoft Exchange Search Host Controller service if it is causing an issue. In some cases it can consume an extremely high amount of memory causing the "Microsoft Exchange RPC Client Access" to fail and get stuck in a starting state. In which case the best solutions are to:

  • Increase the amount of RAM on the server.
  • Set the server to restart when "Microsoft Exchange RPC Client Access" fails. 
  • Disable the "Microsoft Exchange Search Host Controller service".

This is an obvious flaw in the design of exchange 2013 server.

Step by Step install of CentOS 6.3 on Microsoft Hyper-V Server with Linux Integration Services Version 3.4

Create new VHD w/ Legacy Network Adapter for CentOS 6.3

Download CentOS 6.3-minimal.iso (insert disk & install)

Download LinuxICv34.iso (insert disk)

 mkdir -p /mnt/cdrom
 mount /dev/cdrom /mnt/cdrom
 cp -rp /mnt/cdrom /opt/linux_ic
 umount /mnt/cdrom
 cd /opt/linux_ic/RHEL63
 ./install.sh

Once the install is done, shutdown the VPS, note the mac address and then remove the legacy adapter.

Add a standard network adapter with static mac previously noted. apply and restart the VPS

Update your network settings via vi

 vi /etc/sysconfig/network-scripts/ifcfg-eth0

use "i" to insert text, (esc) to exit and ":wq" to write your changes.

It should look something like this:

 DEVICE="eth0"

 BOOTPROTO=none

 ONBOOT="yes"

 TYPE="Ethernet"

 HWADDR=(MAC ADDRESS, This should match what is configured in Hyper-V)

 IPADDR=(YOUR SERVER IP)

 GATEWAY=(YOUR DEFAULT GATEWAY)

 DNS1=(PRIMARY DNS SERVER IP)

 DNS2=(SECONDARY DNS SERVER IP)

 Networking=yes

If your system is still not online for static IP do this:

 ifconfig eth0 (IP) netmask (MASK) up

 service network restart

X

Shawn Hyde ∙ Contact

Comments :


Name :  
 
Phone :

Email :  
 
Subject :