diff --git a/README.md b/README.md
index 045bd4c..07c41b1 100644
--- a/README.md
+++ b/README.md
@@ -90,14 +90,14 @@ If you are unfamiliar with the Solace message router, or would prefer an adminis
 
 ![alt text](images/azure-soladmin.png "soladmin connection to gce")
 
-To manage the currently AD-Active VMR, you can open a CLI SSH connection (on port 2222) or connect SolAdmin (on port 8080) to the Public IP Address associated with the Load Balancer as the admin user. From the Resource Group view for your deployment on the Azure Portal, the Load Balancer is the resource named `myLB`, and its Public IP Address is the resource named `myLBPublicIPD`, which has an IP address and a DNS name that you can connect to.
+To manage the currently AD-Active VMR, you can open a CLI SSH connection (on port 2222) or connect SolAdmin (on port 8080) to the Public IP Address associated with the Load Balancer as the 'admin' user. From the Resource Group view for your deployment on the Azure Portal, the Load Balancer is the resource named `myLB`, and its Public IP Address is the resource named `myLBPublicIPD`, which has an IP address and a DNS name that you can connect to.
 
 
 # Testing data access to the VMR
 
 To test data traffic though the newly created VMR instance, visit the Solace developer portal and and select your preferred programming language to [send and receive messages](http://dev.solace.com/get-started/send-receive-messages/). Under each language there is a Publish/Subscribe tutorial that will help you get started.
 
-To connect to the currently AD-Active VMR for messaging, use the Public IP Address associated with the Load Balancer as the admin user. From the Resource Group view for your deployment on the Azure Portal, the Load Balancer is the resource named `myLB`, and its Public IP Address is the resource named `myLBPublicIPD`, which has an IP address and a DNS name that you can connect to.
+To connect to the currently AD-Active VMR for messaging, use the Public IP Address associated with the Load Balancer. From the Resource Group view for your deployment on the Azure Portal, the Load Balancer is the resource named `myLB`, and its Public IP Address is the resource named `myLBPublicIPD`, which has an IP address and a DNS name that you can connect to.
 
 ![alt text](images/solace_tutorial.png "getting started publish/subscribe")
 
diff --git a/metadata.json b/metadata.json
index 5027d13..7053378 100644
--- a/metadata.json
+++ b/metadata.json
@@ -3,5 +3,5 @@
   "description": "This template allows you to deploy either a standalone Solace Message Router or a three node High Availability cluster of Solace Message Routers onto Azure Linux VM(s).",
   "summary": "This template deploys either a standalone Solace Message Router or a three node High Availability cluster of Solace Message Routers onto Azure Linux VM(s).",
   "githubUsername": "KenBarr",
-  "dateUpdated": "28/09/2017"
+  "dateUpdated": "31/01/2018"
 }
\ No newline at end of file
diff --git a/scripts/deploy_vmr.sh b/scripts/deploy_vmr.sh
index ca08c7c..6c47541 100644
--- a/scripts/deploy_vmr.sh
+++ b/scripts/deploy_vmr.sh
@@ -107,7 +107,9 @@ while [ $LOOP_COUNT -lt 3 ]; do
   fi
   if [ ${LOCAL_MD5_SUM} == ${MD5_SUM_OTHER} ]; then
     echo "`date` INFO: Successfully downloaded ${SolOS_OTHER_LOAD}"
-    isEval=1
+    if [[ $(basename ${solace_url}) != *"-vmr-community"* ]]; then
+        isEval=1
+    fi
     break
   fi
   echo "`date` WARNING: CORRUPT SolOS load re-try ${LOOP_COUNT}"