You cannot!

You need to rename the user from one to another ( this moves all the documents for that user ) 

If the Rename process does not work , you will need to run this on the SQL Server to find out any unlocked documents 

SELECT * FROM MHGROUP.DOCMASTER (NOLOCK) WHERE OPERATOR = N’JSMITH’ OR AUTHOR = N’JSMITH’ OR LASTUSER = N’JSMITH’

 

 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)
When trying to install some software for a user on a Terminal Server the following error comes up : 

enter image description here

You will need to change the following Registry


[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer] "DisableMSI"=dword:00000000
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

If you are looking to Migrate a classic VM in Azure to ARM , you will need to change your Endpoint port forwards via a Load Balancer

Go to the Azure portal: http://portal.azure.com

Click “NEW” -> write “Load Balancer” in search field -> Click “Load Balancer”

After you have clicked the “Load Balancer”, click the “Create” button.

Then fill out the configuration blade as shown below:

Azure will take a few minutes to create the Load Balancer.

 

Once created, your resource group will look like this:

Step 2: Configure Load Balancer Backend Pool

In order to connect our newly created load balancer to our virtual machines, we need to create a so-called “Backend Pool”.

To do so click on your load balancer to open its configuration blade.

Click on the item called “Backend Pool” in the menu to the left:

Then click the “Add” button:

 

 

Fill out the “Add backend pool” configuration blade as shown below:


Now click on “+ Add a target network IP configuration”:

 

 

…and select the IP configuration for your virtual machine:

 

 

Finally, click the “OK” button to save the Backend Pool.

Now repeat this step;  but this time choose VM1 instead of VM0.

All in all, this will give us two backend pools pointing to VM0 and VM1 respectively:

It will take Azure 1-2 minutes to create the Backend Pools

Step 3: Configure NAT rules

Now our load balancer is connected to our virtual machine and we now need to configure rules for redirecting network traffic.

Start by clicking “Inbound NAT Rules” in the menu to the left:

Then click the “Add” button:

Fill out the “Add inbound NAT rule” configuration blade as shown below:

 

Now repeat this step, but this time choose VM1 instead of VM0 .

We will now end up with two Inbound NAT Rules: one with port 8088 associated to VM0 and one with port 8089 associates to VM1 :

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

If you are using Windows 10 or have Powershell 5 installed run

Install-Module AzureRM

Once installed, use the following to log into Azure in an interactive fashion:

 
Login-AzureRmAccount

Edit these lines , use Get-AzureRmVirtualNetwork to get your VirtualNetwork Name

Run these 

$vmName = “%vmname%”
$resourceGroupName = “%resourcename%”

$virtualNetworkName = “%virtualnetworkname%”
$locationName = “australiaeast”
$vmsize = “Standard_A1”
$destinationVhd = “https://vmname.blob.core.windows.net/vhds/osdisk.vhd”

$virtualNetwork = Get-AzureRmVirtualNetwork -ResourceGroupName $resourceGroupName -Name $virtualNetworkName
$publicIp = New-AzureRmPublicIpAddress -Name $vmName -ResourceGroupName $ResourceGroupName -Location $locationName -AllocationMethod Dynamic
$networkInterface = New-AzureRmNetworkInterface -ResourceGroupName $resourceGroupName -Name $vmName -Location $locationName -SubnetId $virtualNetwork.Subnets[0].Id -PublicIpAddressId $publicIp.Id
$vmConfig = New-AzureRmVMConfig -VMName $vmName -VMSize $vmsize
$vmConfig = Add-AzureRmVMNetworkInterface -VM $vmConfig -Id $networkInterface.Id
$vmConfig = Set-AzureRmVMOSDisk -VM $vmConfig -Name $vmName -VhdUri $destinationVhd -CreateOption Attach -Windows
$vm = New-AzureRmVM -VM $vmConfig -Location $locationName -ResourceGroupName $resourceGroupName

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

I was trying to copy an Azure VM Hard Drive from a classic storage account to a new storage account , however after shutting down the VM I was getting the error

Copy status: Failed; Description: 412 ConditionNotMet “Copy failed when reading the source.”.

I contacted Azure support who notified me to use the below

VHD is attached to VM, and then you can refer to the following steps to copy it:

  1. Download and install  Microsoft Azure Storage Explorer.
  2. Click Storage accounts on the left pane on Azure Portal> Click on the name of the corresponding storage account>Keys>Copy the primary key
  3. Open the tool Azure Storage Explorer, and follow the steps below to connect to the target and destination storage accounts

After both storage accounts get connected, you can go find the corresponding vhd file and copy it, and then go to the destination container of the storage account to paste the copied file

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Make sure your Avaya phone system has been setup with a routeable DNS Server per http://pariswells.com/blog/random/avaya-ip-office-default-gateway

Create a user in 365 with a License 

On the IP Office under the SMTP Tab put the following:
Server Address – smtp.office365.com
Port – 587 – Mine was intermittently working with 25 so I switched it and it has worked on 587.
Email From Address – voicemail@company.com
Use STARTTLS – Checked
Server Requires Auth – Checked
Username – adminaccount@company.com
Password – admin accounts password
Use CRAM-MD5 – Unchecked

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Citrix XTE Service

Identified that the CITRIX XTE SERVER service terminated unexpectedly.

Solution/workaround

  • Renamed the httpd.conf file in this directory C:\Program Files (x86)\Citrix\XTE\conf
  • Copied the httpd.conf file from a working server
  • Restarted the Citrix Xte Server Service

New sessions and existing sessions can now be established 

Current investigating the cause of the issue to ensure it will not happen again

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently I had a customer needing to take custom amounts decided by the customer through a Stripe Payment on his wordpress Site, however he needed to take multi currencies

The WordPress Stripe Plugin backend only allows you to set one currency to the below will bring up your site currency

<p style=”text-align: left;”><a href=”https://domain.com/stripe-payment-terminal/”>
</a>[accept_stripe_payment name=”Payment” button_text=”PayNow” billing_address=”1″ ]</p>

To get a new currency to show, add Currency=’New Currency Code’

<p style=”text-align: left;”><a href=”https://domain.com/stripe-payment-terminal/”>
</a>[accept_stripe_payment name=”Payment” button_text=”PayNow” billing_address=”1″ currency=”EUR” ]</p>

 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

If one of your drives have failed in a dell server probably with a E1810 Error , you will need to replace the drive.To skip the error and allow the server to boot and Bypass :

There are offline or missing virtual drives with preserved cache. Please check the cables and ensure that all drives are present.

Press Ctrl R to go to the PERC Bios, clear the cache in the PERC BIOS. To clear the cache, you navigate to the screen that has the tree structure of disk groups and virtual disks. Then navigate by up-arrow until you are on the root of the tree structure, which will be the PERC H710 Mini and not a specific disk group. Press F2 which gets you to a screen that allows you to manage the cache. That will allow you to clear the cache.

Exit by hitting ESC and then control-alt-del to reboot.

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)