Let me say that I love Box.com. It allows me to have a great number of features for my computer storage needs. One of them is to host all my production videos and files across all my computers. But one annoying issue was how to move it to another drive.
My C drive was hitting 100% utilization just from booting up my PC. I check Antivirus, change SSD drives, Reimage the machine 4 times and I have a decent machine with 16 cores and 256GB of RAM, but the Boxdrive was still using all the time the C:\
My app where dog slow. To open Photoshop or Any app will take 30 – 60 seconds.
So when I start checking the Boxdrive binaries were using 100% of the C:\.
I figured if this can be moved to another drive, the problem will go away. So after several tryies, I figured out a solution.
Based on their FAQ it is not possible to move the Boxdrive location to another drive. But I figure it out. Yeap.
I will give you the simple steps to fix your Boxdrive client to and move it to another drive.
NOTE: By the way, this is not supported by Box so if you call them they may not support you but this fixed my issue.
1 . Uninstall Boxdrive
2 . Create Symlink for Boxdrive location.
Open command prompt (not powershell)
mkdir D:\Box (this will be the drive and location where you want your box data to be)
In the windows world, you normally connect via the RDP protocol to your servers. If you want to secure the network you can use a Remote Desktop Gateway in order to provide access to your servers and control who can get access.
1 . Configure your RDP client with the correct IP address of the server that you want to connect to.
2. You should have a Gateway Settings tab. Type the RDS Gateway server IP address or dns name.
That’s it. You will be connected to your environment via the Remote Desktop Gateway Server.
In every environment you may have different devices and appliances that may need to send email or notifications. This guide will go thru the process on how to configure your Linux server with Postfix Mail Transfer Agent. Thru the guide I will use Ubuntu as the Linux distribution for the demo.
1. Make sure to configure Exchange to accept email for relay. Check this post for how to configure Exchange 2013 to relay your mail for appliances.
2. Install all the required packages. ex. sudo apt-get install mailutils
3. During the installation it will ask to configure the basic settings for Postfix. Select Satellite system. This mean your linux system is not managing email it is just sending it out.
4. Type your domain fqdn in the next screen. Ex. domain.com
5. Type the IP address of your Exchange 2013 server hosting the receive connector. Ex. 111.222.333.123
6. After the installation finishes. You need to reconfigure Postfix. To reconfigure Postfix execute the following command: sudo dpk-reconfigure postfix
7. Press OK.
8 . Click Satellite system –> TAB –> OK
9. validate the domain is correct. Press OK.
10. Check that you have the correct IP Address for the Exchange Server.
11.Type the email address for the administrator
12. Erase all the destinations. This will force all the email to go out and not accept any email.
13. In the Force Synchronous updates on mail queue, select Yes
14. Because we are only sending email out, tab to OK.
15. Leave the mailbox size on 0.
16. Leave the local address extension + and tab to OK.
17. Tab to ipv4 and then select OK.
18. After it finishes reconfiguring. You can try your new setup. ex. echo “Hi” | mail -s “Testing” email@example.com
19. You should see your email coming into Exchange. By default is comes with the servername as the domain.
Microsoft released the Technical preview of their new Operating Systems. (Details Here) If you are like most IT Professionals, you may have downloaded the preview and try to use it for your basic computing environment. After playing with the new UI for a little bit, I installed the Cisco Anyconnect client and tried to connect to my office VPN. The connection failed with the following error: “Failed to initialized connection subsystem”.
After troubleshooting the issue for a little bit, I found a fix for the issue. Here are the steps to fix your Cisco AnyConnect client running on Windows 10 Preview.
1 . Open and explorer window and go to c:program files (x86)CiscoCisco AnyConnect Secure Mobility Client
2 . Right click vpnui.exe and click properties.
3 . Click the Compatibility tab, then click Run this program in compatibility mode for: and select Windows 8. Then Click OK.
4 . Click the Windows Logo and Click the Cisco AnyConnect Icon.
5 . In the Cisco AnyConnect client type your VPN server FQDN or IP address. Ex: vpn.domain.com
6. Type your username and password
7. Your client should connect successfully to your Cisco VPN appliance.
8 . After your client finishes the connection you should see a green check mark in the lock.
Hope this helps you test Windows 10 with your corporate images. If you have any questions please leave a comment.
The new Hitachi Content Platform version 7 is out and it is packed with several new features and enhancements. One of the new features is the DNS functionality. The new built-in DNS services drop the dependency on external DNS servers for DNS queries for the Tenants or namespace. The way to configure DNS in HCP 7 is by configuring a secondary DNS zone in the Windows servers and referring to the HCP nodes as the Primary Zone masters.
I decided to automate the process to help with the installation and configuration of the HCP into a customer environment. The video goes thru the process of executing the PowerShell script that will configure everything needed for a new HCP 7 setup.
[code language = ps]
# ScriptName: Configure-DNS-Zone-HCP7.ps1
# Author: Carlos Vargas
# Contact: carlos dot vargas at hds dot com
# Info: This script will configure the HCP DNS zone in
# a Windows DNS server
# Version: 1
# Script to create DNS records for HCP 7
Write-Host “HCP 7 DNS Zone Configuration Script for Windows” -ForegroundColor Yellow
Write-Host “Version 1.0” -ForegroundColor Yellow
# Select DNS Zone for HCP nodes A Records
Write-Host “Please Select the DNS Zone where you want to create your HCP Nodes A Records” -ForegroundColor Yellow
$SelectedDNSZone = GetDNSZones
# Collect Information about HCP Nodes
$hcpnodeminip = Read-Host “Type the IP Address of your first HCP Node. Ex: 192.168.2.10”
$hcpdnsservername = Read-Host “Type the Host name to use as reference for the HCP node. Ex: hcp-node-001”
# Create HCP-Nodes in DNS to reference secondary zone from HCP
Add-DnsServerResourceRecordA -Name $hcpdnsservername -ZoneName $SelectedDNSZone -IPv4Address $hcpnodeminip
# Validate Record Created
#Get-DnsServerResourceRecord -Name $hcpdnsservername -ZoneName $SelectedDNSZone
# Create Secondary Zone pointing to HCP nodes
$hcpdnszonename = Read-Host “Type the name of the HCP cluster DNS zone. Ex: hcp7.domain.com”
$hcpdnszonefile = “$hcpdnszonename.dns”
Add-DnsServerSecondaryZone -name $hcpdnszonename -ZoneFile $hcpdnszonefile -MasterServers $hcpnodeminip
# Open HCP Admin Portal via new DNS Zone name
$hcpadminportalurl = “https://admin.$hcpdnszonename”+”:8000″
One of the best features in Microsoft Windows Server 2012/R2 and Hyper-V Server 2012/R2 is the ability to connect a VM directly to your Fiber Channel Storage Array. This feature is called Virtual HBA or vSAN. In order to get this feature working we need to follow a couple of simple steps to enable it on your servers.
Video to Configure Hyper-V vSAN
Steps to configure our Hitachi FC cards for Hyper-V 2012/R2 vSAN
1. Open an administrator command prompt
2. Change to the HFCtools directory. cd c:program files (x86)HitachidrivershbaHFCtools
3. Enable NPIV function. hfcmgr -p all npiv enable
4. Reboot the server.
5. After the server is back online, Open your Hyper-V Manager
6. Right Click your server and click Virtual SAN Manager
7. You should be able to create a vSAN
If you see this error when you open your Virtual SAN manager you need to enable your Fiber Channel card NPIV features
Now we have your Client Hyper-V installed and the network configured. The next step is to create a virtual machine so you can use it as a template. We will go thru the process on creating your first virtual machine.
1. In your Hyper-V Manager Application, Right Click in your computer name, then click new >Virtual Machine
2. The New Virtual Machine Wizard will start. Press Next.
3. Type a name for your VM. I selected to store the virtual machine in a separated folder to make it easier to move later. Then press Next>.
4. Select Generation 2 for your VM type and press Next>.
5. For this example I will use Windows Server 2012 so we can use Dynamic Memory. Leave the default settings for memory and press Next>.
6. Select your Network Switch. If you followed my post on Configuring Network for Windows 8.1 Client Hyper-V you will see the Internal Switch. Then click Next>.
7. In the Connect Virtual Hard Disk screen you can select the size for the VM storage. By default this will be a differencing disk so you will not allocate all the storage to the VM. Only what is consumed. Type the amount you want in GB then press Next>.
8. Leave the default to install an operating system later and press Next>.
9. Press Finish and your VM will be created with all the parameters you just specified.
You have a fully functional Client Hyper-V machine, with network and a virtual machine. In the next post we will install the Windows 2012 R2 operating system.