TF259137: The following account does not have sufficient permissions to complete the operation: domain\user. The following permissions are needed to perform this operation: Create.

When importing virtual machine in MTM Lab Center you may encounter error message below:

TF259137: The following account does not have sufficient permissions to complete the operation: domain\user. The following permissions are needed to perform this operation: Create.

From what I know there is no UI that would allow the TFS admin to grant the necessary privileges related to library management. To fix this, do:

1. Open a console where tfslabconfig.exe. In VS 2013 with MTM installed, it is located in C:\Program Files\Microsoft Visual Studio 12.0\Common7\IDE.
2. Run the following command:

TfsLabConfig Permissions /collection:http://[TFSMachineName]:8080/TFS/DefaultCollection /user:domain\user /allow:create,Read,ManageLocation,Write,edit,delete,start,stop,ManagePermissions,ManageChildPermissions,Pause,ManageSnapshots

Of course you have to replace [TFSMachineName] with the name of your TFS Server and this has to be run by user with TFS admin rights. You also have to change DefaultCollection and domain\user.

References:
http://social.msdn.microsoft.com/Forums/vstudio/en-US/0f2a3f3b-48a0-4bd8-b03a-c8a4ebf03da2/import-vm-template-in-lab-center

Get Linux user id

Linux user ID can be used in say mounting a CIFS share, see link. To get user id, do:

$: id timus

This will print UID and GID of user timus.

Check version of VirtualBox guest additions installed

$: locate vboxguest

If this returns nothing either you don't have VirtualBox guest additions installed or you need to update the database used by locate. If you suspect that the database may need a refresh, you can do sudo updatedb.

Alternatively, you can check contents of /opt. If you have the additions installed, it should have an entry like VBoxGuestAdditions*.

Mounting a Windows share using smbfs with read-write access

To mount a Windows share using smbfs do the following:

#: mount -t cifs -o username=your_user_name,uid=1000 //machine_name/share_name  /mnt/point

Or the old style:

#: mount -t smbfs -o username=your_user_name,uid=1000 //machine_name/share_name  /mnt/point

Note here that uid=1000 is not a magic number but rather your linux userid. You can get this value from passwd file normally located in /etc/passwd. The user with uid=1000 should be able to manipulate files pointed to by //machine_name/share.
And when connecting to a share that is mananged by Active Directory, need to escape the backslash for it to work, e.g.:

#: mount -t smbfs -o username=domain-name\\username,uid=1000 //machine_name/share_name  /mnt/point

Notes:
Need to install smbfs for this to work, like (Debian/Ubuntu):

#: sudo apt-get install cifs-utils

~ts~

ERROR: No configuration file found when booting Ubuntu 13.04 using USB stick

I created a boot-able network install of Ubuntu 13.04 on USB stick using Pendrive's Universal USB Installer (Universal-USB-Installer-1.9.3.9.exe). Booting this USB stick on my old Eee PC 900 shows "ERROR: No configuration file found". To fix this rename/copy isolinux.cfg to syslinux.cfg.

As an alternative to Universal USB Installer, you may try Unetbootin(http://unetbootin.sourceforge.net/)

Reference(s):
http://www.pendrivelinux.com/error-could-not-find-kernel-image-linux/

PS Quick Tips: Format datetime with milliseconds

(Get-Process)[0].StartTime.ToString("yyyy/MM/dd HH:mm:ss.fffff")

This displays when the process at index zero was started with milliseconds information

PS Quick Tips: Display service start times

PS C:\> Get-WmiObject win32_service | Where-Object {$_.State -eq "Running"} | ForEach-Object {Write-Host ((Get-process -id $_.ProcessId).StartTime)","$_.PathName","$_.DisplayName}

Run this in elevated prompt to get correct information.

PS C:\> Get-WmiObject win32_service | Where-Object {$_.State -eq "Running"} | ForEach-Object {Write-Host ((Get-process -id $_.ProcessId).StartTime.ToString("yyyy/MM/dd HH:mm:ss.fffff"))","$_.PathName","$_.DisplayName}

This add milliseconds to the service information

Keywords:

PowerShell

Process start times