After much searching I found some formats that work, but have not found a good reference document.
To modify the format of a date or time, convert the column to text and apply these formats as needed.
| Month | m, mm |
| Day | d, dd |
| Year | yy, yyyy |
| Hour | h, hh |
| Minute | m, mm |
| Second | s, ss |
| AM/PM | AM/PM |
Of course you need to go into SharePoint Designer and do a nowrap=”true” on the <td> if the date renders on 2 lines.
I’ve run into a bug with VirtualBox and at least Windows XP where trying to reboot or shutdown the VM causes the shutdown process to hang at the screen displaying: Windows is shutting down. This problem has to do with mouse pointer integration.
To fix the problem:
At this point shutting down or restarting the VM should not hang. Thanks to this post for pointing me in the right direction.
To set the default Storage Repository (SR) in XenServer:
You can also right click on the Storage in XenCenter and select Set as Default.
In either case, this is helpful if your default SR is the smallest disk on the server, and you are doing P2V operations.
After enough struggling, I have learned enough to get Windows XP working within XenDesktop.
Here are the steps I’ve taken and the errors I’ve faced as well as the solutions to those errors:
Before using XenConvert on a physical source machine, there are a couple preparations:
Use the MOUNTVOL /E command in a cmd window to enable Windows Automount
This article describes disabling Windows Autoplay (Autorun): http://support.microsoft.com/kb/967715
On Windows Server 2003 change this registry key value to FF:
HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionpoliciesExplorerNoDriveTypeAutorunOn one server, the key didn’t exist. I ignored disabling autoplay on that server and the export worked out anyway.
These are obvious, uninstall VMWare, VirtualPC, VirtualBox, etc. Find a spot to drop the OVF or VHD package.
We weren’t doing anything fancy with our interfaces, so I ignored this. I figure if you are using a Network Interface Team, you would know it. Feel free to shoot me a comment on this if you have any insight.
I currently have the opportunity to use the XenConvert tool to move some physical servers to our customer’s XenServer environment. I have finished moving the first server, but I had to take a couple passes before finding a successful p2v plan.
My first plan was to export an OVA file, transfer it to an existing VM on XenServer. Then use XenCenter to import the .ova file. Using the .ova approach is done by selecting Open Virtualization Format (OVF) Package and ticking the Create Open Virtual Appliance checkbox in the XenConvert workload screen.
Well the XenConvert to .ova finished successfully. But importing the .ova file using XenCenter failed. It kept failing on the EULA which wasn’t defined, nor necessary to define when exporting.
This initial error using XenCenter led me to try importing with XenConvert. It was a good idea, but reality didn’t play out, and I received an error again.
My second plan was to just export the VHD. Again using XenConvert, I select the To: XenServer Virtual Hard Disk (VHD) in the initial workload screen. Again this conversion to a .vhd file completed successfully. After transferring to the existing VM on XenServer, I immediately went to XenConvert instead of XenCenter.
In XenConvert on the initial workload screen, I selected From: Microsoft Virtual Hard Disk (VHD) and To: XenServer. Selected the .vhd file from the file system. And filled in the Hostname, User name, Password and Workspace values in the XenServer connection parameters screen:
This worked.
My third plan was to export an OVF package.
This was never executed because the VHD approach worked. I will try this approach for the second server I am moving, so watch for updates on this post.
I have successfully imported the 3rd server using an OVF and XenConvert. I found that if the OVF fails, then the VHD method will likely fail as well. It boils down to having enough disk space to do the convert. I didn’t see much advantage to using the OVF. The OVF did allocate more RAM up front, but only provided 1 VCPU. I still had to manually configure dynamic RAM and allocate more VCPU after installing Xen Tools.
Installing BPC NetWeaver Support Packages are a bit more involved than for the MS version. There are 2 parts to address: the ABAP SP and the BPC SP.
Before beginning, document the current install by making screen shots of the Server Manager screens into WordPad.
ABAP SP
For the ABAP SP retrieve the .SAR file from the SAP Marketplace
NOTE: ABAP BPC Support Packages are NOT cumulative, so download all the SPs between your current version and the latest.
NOTE with Solution Manager, you can retreive the SP directly thru NetWeaver.
Load the Support Package into NetWeaver
Transport SP into the system
BPC .NET SP
For the BPC SP retrieve the .exe file from the SAP Marketplace
NOTE: BPC .NET Support Packages are cumulative, so only download the latest.
Install the SP
While testing a new installation of BPC, I encounter an error processing an Application:
Cannot find the object “ApShellExtra.dbo.AuditActivityHdrApShell” because it does not exist or you do not have permissions.
Sure enough SQL Server Management Studio shows the table is not there. On a whim I restart the Admin client and try processing the Application again; it works!?
Turns out, after the install I always modify security to allow the BPCSysAdmin account to have full control over ApShell. Apparently those security changes weren’t completely applied until I restarted.
After installing BPC 7.0 MS the Management Console wouldn’t let me view logging. The ‘User does not exist’ error would appear. This was a Windows Server 2003 R2 dual server environment. Using Fiddler I was seeing a 500 error, with something like ‘cannot resolve server name vmw2317’. Hmmm… vmw seems like VMWare, but I was dealing with physical servers.
Looking at the web.config file, I discovered several appSettings with vmw2317 and vmw2315; these were left over by SAP during development. Changed the names to our real server names, saved the file and everything works!
