210 SW Everett Mall Way Suite A
Everett, WA 98204
425-513-1888
425-513-1511 Fax
Visit us on the Web at RenegadeClassicsEverett.com
I have to hand it to Renegade. I purchased a really nice leather jacket up at their Everett store, here about 3 months ago. I rode daily after that, and I’m pretty hard on my gear, I guess, because in that time, I sheared two clasps (shoulder and wrist), and one of the zippers.
I was fully expecting to pay a seamstress when I brought it back by to make the repairs. As it turns out, Renegade covered all the work under warranty! And since the zipper cannot be repaired, they are ordering and replacing the jacket! I can’t say enough about these guys, they stand behind their product 110%. HIGHLY RECOMMENDED!
I know this is a technical blog, but this kind of business ethic must be appreciated, and many companies would find themselves with loyal customers if they followed this example.
This is a procedure I’ve had to use a lot of times. Credit to the following blog for this information. Repeated here, so it’s not lost and for my quick reference.
http://blogs.msdn.com/b/tonyschr/archive/2004/04/19/116245.aspx
Let’s say you’re in a situation where you can’t log into your XP machine because you forgot to click that checkbox. psexec to the rescue!
psexec \\machinename reg add “hklm\system\currentcontrolset\control\terminal server” /f /v fDenyTSConnections /t REG_DWORD /d 0
I shouldn’t have to say that this isn’t in any way supported, or that it’s not going to work if you’re not already an admin on the machine that has RD access, or that a firewall will get in the way, or that there may be better ways to do it using script or WMI, but I’ve found it useful on a couple occasions.
Thanks goes out to vlho in this thread for this information. For editing MSI files, I prefer the FREE Orca, which can be downloaded here. It is duplicated here:
Warning: This hacking is not supported by VMware !
1/ extract iso image of vCenter (e.g. in 7zip) to any folder in destination machine
2/ download application for editing msi file and install
e.g. Insted from http://www.instedit.com/download.html
3/ run this application and open file …\vpx\VMware vCenter Server.msi
4/ in Tables click on item “LaunchCondition”
5/ on the right find row with text:
“Installed Or (VersionNT>=501 And VersionNT < 600) Or (VersionNT = 600 And MsiNTProductType <> 1) Or (VersionNT = 601 And MsiNTProductType = 3)”
and modify it to:
“Installed Or (VersionNT>=501) Or (VersionNT = 600 And MsiNTProductType 1) Or (VersionNT = 601 And MsiNTProductType = 3)”
after that save and close
6/ download 64-bit verison of Microsoft AD LDS (new name for ADAM) from:
Windows Vista:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=e1b7f0a5-2131-44fd-9dde-fa146154e13a
Windows 7:
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=a45059af-47a8-4c96-afe3-93dab7b5b658
and install
7/ run ..\autorun.exe to install vCenter
…
good luck
Edit: Screenshot below of the LaunchCondition table as seen in Orca:
09/27/11 – Please see below comments for ESX 5. The link ishttp://communities.vmware.com/docs/DOC-16950
Regurgitation continues…
Some vendors license their application per processor, also in a virtualized environment. So if your VM has 4 vCPU’s your vendor will want you to buy a 4 processor license for the application. But you can avoid this by telling the VM that it has cores instead of processors. In others words, instead of having 4 processors you would have 1 processor with 4 cores:
1. Power off the VM
2. Right click on the VM and select “Edit Settings…”
3. Select the “Options” tab
4. Click on “General” (in the “Advanced” options section)
5. Click “Configuration Parameters…” (in the pane on the right)
6. Click “Add Row”
7. Enter “cpuid.coresPerSocket” in the “Name” column
8. Enter a value (try 2, 4, or 
in the “Value” column
9. Click “OK”
10. Power on the VM
The VM will now appear to the OS as having multi-core CPUs with the number of cores per CPU given by the value that you selected. For example, if you create an 8 VCPU VM and set “cpuid.coresPerSocket = 2″ it will be recognized as 4 dual-core CPU’s by the OS while it’s actually utilizing 8 physical cores.
Keep in mind that this feature is currently unsupported!
OK, so we have recovered files from the server from a flat file copy, yay! Now this article is being written assuming that you do not have a corrupted database here! So once you have the Sharepoint database files copied over, you will need to download a copy of (currently), SQL 2005 Express SP4.
After installing, we need a way to attach the database, so download a copy of SQL Server Management Studio Express, and we are good to go. During the install, grant yourself sys admin role rights. Just to make sure, when I’m fine, I run the surface configuration to make sure I have rights.
Open Studio Manager and connect. Right click databases and attach. I copied my MDF and LDF to the location SQL is looking for it. Just click Add MDF and you will see the full path. Once the database is attached, lets get busy!
Now download Sharepoint Exporter. Open it and use your computer name, backslash, instance name (should be SQLEXPRESS). You’re in the database name and you can now export from your database to the file system!
Copy the c:\bbnt\ folder, binary included, from another server, and then from a command prompt:
c:
cd \bbnt
bbnt -y -install 137.238.1.200 Y
The IP 137.238.1.200 should be the same as your BBDISPLAY server. Now, in Server 2008, make sure that you command prompt window was launched with administrative privileges.
I’ve seen a bunch of articles out there on how to properly redirect OWA in SBS, and all of them are wrong! They are on the right path, but none of them have the definitive answer, which is right here in front of you! First of all, the real answer is in how you plan to use SBS. If you are happy with just accessing http://remote.company.com/remote, http://remote.company.com/owa and http://remote.company.com:987, then this article is not for you. I prefer:
OWA – https://mail.company.com
RWW – https://remote.company.com
Sharepoint – https://sharepoint.company.com
(more…)
This powershell command grants an administrator access to all mailboxes across the database:
get-mailbox -server| Add-MailboxPermission -User “domain\userid” -AccessRights FullAccess,SendAs
* To get the changes to take effect, restart the Information Store Service.
