I love SBS 2011 and the way you can have shared folder display in your RWW.
However sometimes a folder is displayed there you may not want. Like QuickBooks etc. Here is a way to control what folders are displayed there. You can also display folders from other server using this method also.
On the SBS 2011 server go to
C:\Program Files\Windows Small Business Server\Bin\WebApp\RemoteAccess
Make a backup copy of web.config file
Open web.config in notepad or an in something like Dreamweaver, and do a search for SBSStorageProvider
Replace this line…
<wssg.storageProvider type=”Microsoft.WindowsServerSolutions.Web.Storage.SBSStorageProvider, Wssg.Web.StorageProvider” />
With this line
<wssg.storageProvider type=”Microsoft.WindowsServerSolutions.Web.Storage.FileSystemBasedStorageInformationProvider, Wssg.Web.Internal” shares=”\\Servername\Sharename0;\\Servername\Sharename1;\\servername\Sharename2″ />
Of course put in your own Server and Share Names in there.
Comments Off
I installed ESXi 5.0 on a system that had ESXi 4.1 on it. I did a clean install. When I got done with the install (installed on a USB drive) I configured the storage a raid 5 array with a hot spare I still had an error. I did a little research and found this post (see link below). That got me thinking that it would be better to redirect the logs to a HDD instead of a USB or SD drive anyway so I change the path in the Globe settings and now the logs write to the main datastore instead of the USB or SD drive. This also makes the logs much more accessible.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2006834
Comments Off
I got “cannot configure backup schedule” when trying to add a new second drive to the server.
I tried everything I could think of and the last item on this KB worked for me.
http://support.microsoft.com/kb/2009365
Option 3
Add a new disk to the backup schedule by running the wbadmin command from an elevated command prompt.
1.Run the following command from an elevated command prompt to determine the Disk Identifier of the new disk:
wbadmin get disks
2.Based on the output, locate the disk that will be added to the scheduled backup. Make a note of the Disk Identifier. The output will resemble the following:
Disk name: xxxxxxxxxxx
Disk number: x
Disk identifier: {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
Total space: xxx.xx GB
Used space : xxx.xx GB
3.Run the following command to add the new disk to the Scheduled backup. Use the Disk Identifier from the previous step as the “AddTarget” parameter.
WBADMIN ENABLE BACKUP -addtarget:{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
4.When you receive the following prompt, type Y for Yes.
“Do you want to enable scheduled backups with the above settings?”
Comments Off
VMware announce a new pricing model today. I do understand why they did it I am just not sure if it was the smartest thing to do. Only time will tell.
I have been around long enough to remember Novell. My first Novell install was 2.15 far different from anything today. That is when you ran the whole server on 4MB of RAM. Not to say they have completely gone away but look at them now. When Microsoft entered the Server game everyone thought they were wasting their time. Let’s face it Novell had it all raped up. Now look at them. It was not Microsoft that kill Novell it was Novell committed suicide.
The CFO will look at the bottom line. If Microsoft can get them where they need to go for far less money who do you think will win in the long run.
I know I do not want to be running my virtual environment on a Windows platform but that might be the future. Then again there are other players. Maybe it is time to look at Xen. Not because VMware will cost more for my customers it is more will this be the start of a slow death for VMware. I hope not I love this product too much.
I migrated a SBS 2008 to SBS 2011 after I migrated the search in Exchange would not function properly.
So I wanted to reset the search index. The way you do this is start Exchange Management Shell and navigate to this folder. Microsoft\Exchange Server\V14\Scripts Normally here. C:\Program Files\Microsoft\Exchange Server\V14\Scripts You rwill need to do somethig like this with the quotes in place.
cd ‘Program Files\Microsoft\Exchange Server\V14\Scripts’
then run the following command: .\ResetSearchIndex.ps1 -force -all
WARNING: Waiting for service ‘Microsoft Exchange Search Indexer (MSExchangeSearch)’ to finish stopping…
MSExchangeSearch service stopped
Deleting catalog for Mailbox Database removing: D:\Exchange Server\Maillbox\catalogdata-….
MSExchangeSearch service Started
You will get an:
Event ID 109 when the full crawl begins.
Event ID 110 when the full crawl ends.
Comments Off
Original Server was Server 2008 32-bit
First I was give a backup file of a WSS 3.0 with the Stsadm utility.
Stsadm -o backup -url http://localhost -filename c:sp_backupsharepoint.bak -overwrit
Then on a new Machine I installed Windows 2008 64-bit and SQL Server 2008 R2 Express 64-bit.
Then I install WSS 3.0 64-Bit and I Created a Site Collection using the same URL of the original server. Then I patched it until it matched the 32-bit WSS 3.0 exactly.
I Configure alternate access mappings to match my backup commend. I was give the backup file without access to the originally Server so I had to match the URL in the originally backup.
Then I restored the backup file with this commend.
stsadm -o restore -url http://localhost -filename C:sp_backupsharepoint.bak -overwrite
Once I had a working site I simply install SharePoint Foundation 2010 and it upgraded the the server. I got a few errors on the upgrade but I am pretty sure they were due to some Custom Web Parts. Except for the custom web parts everything seems to be working fine.
I do not believe this is a supported way of upgrading but it worked for me I am not sure if it will work for you. I was doing this in a virtual environment so I was able to use snap shots which came in handy.
Comments Off
If you SBS you know that your C drive seem to have less and less disk space over time.
Main source of this is WSUS. Ok so we run the cleanup Wizard in WSUS Options. If you have never run this before it may not finish. The trick is it run it one option at a time. Only check one box at a time.
Or you can move the WSUS to another drive. http://blogs.technet.com/b/sbs/archive/2009/09/23/how-to-move-wsus-content-and-database-files-to-a-different-partition.aspx
Also look that this page. http://blogs.technet.com/b/sbs/archive/2010/03/02/recovering-disk-space-on-the-c-drive-in-small-business-server-2008.aspx
Another area is logs. Look here and see how much disk space is being taken up. C:\inetpub\logs\LogFiles
Comments Off
I had this happen today. I accidentally deleted everything except the xxxx-flat.vmdk files. I could just restore this machine but it was a SQL server and would have lost several hours of data. I needed that data so I restored the vmx file and then I deleted the drives and tried to add the xxxx-flat.vmdk files to it. This did not work because there is more to a vmdk file than the xxxx-flat.vmdk files. See below. Saved me and I lost nothing.
********* Taken from VMware Knowledge Base 1002511 *************
To create a virtual machine disk:
- Log in to the terminal of the VMware ESX host.
- Navigate to the directory that contains the virtual machine disk with the missing descriptor file using the command:
cd /vmfs/volumes/myvmfsvolume/mydir
Note:
- If you are using a version of VMware ESXi, you can access and modify files and directories using the VMware vSphere client Datastore Browser or the vifs utility included with the vSphere CLI. For more information, see the section Performing File System Operations in vSphere CLI documentation.
- If you are using VMware Fusion, the default location for the virtual machine files is <home>/Documents/Virtual Machines.localized/<virtual machine>/ folder where <home> is your home folder, and <virtual machine> is the name of the virtual machine.
- Identify the type of SCSI controller the virtual disk is using. You can do this by examining the virtual machine configuration file (.vmx). The controller is identified by the line scsi#.virtualDev, where # is the controller number; there may be more than one controller and controller type attached to the virtual machine. This example uses lsilogic:
scsi0.present = “true”
scsi0.sharedBus = “none”
scsi1.present = “true”
scsi1.sharedBus = “virtual”
scsi1.virtualDev = “lsilogic”
- Identify and record the exact size of the -flat file using a command similar to:
# ls -l vmdisk0-flat.vmdk
-rw——- 1 root root 4294967296 Oct 11 12:30 vmdisk0-flat.vmdk
- Use the vmkfstools command to create a new virtual disk:
# vmkfstools -c 4294967296 -a lsilogic -d thin temp.vmdk
This command uses these flags:
-c <size> (This is the size of the virtual disk).
-a <virtual controller> (Whether the virtual disk was configured to work with BusLogic or LSILogic).
-d thin (This creates the disk in a thin-provisioned format).
Note: To save disk space, we create the disk in a thin-provisioned format using the type thin. The resulting flat file then consumes minimal amounts of space (1MB) instead of immediately assuming the capacity specified with the -c switch. The only consequence, however, is the descriptor file contains an extra line that must be removed manually in a later step.
The files temp.vmdk and temp-flat.vmdk are created as a result.
- Delete temp-flat.vmdk, as it is not needed. Run the command:
# rm temp-flat.vmdk
- Rename temp.vmdk to the name that is required to match the orphaned .flat file (or vmdisk0.vmdk, in this example):
# mv temp.vmdk vmdisk0.vmdk
- Edit the descriptor file with a text editor:
- Under the Extent Description section, change the name of the .flat file to match the orphaned .flat file you have.
- Find and remove the line ddb.thinProvisioned = “1″ if the original .vmdk was not a thin disk. If it was, retain this line.
# Disk DescriptorFile
version=1
CID=fb183c20
parentCID=ffffffff
createType=”vmfs”
# Extent description
RW 8388608 VMFS “vmdisk0-flat.vmdk”
# The Disk Data Base
#DDB
ddb.virtualHWVersion = “4″
ddb.geometry.cylinders = “522″
ddb.geometry.heads = “255″
ddb.geometry.sectors = “63″
ddb.adapterType = “lsilogic”
ddb.thinProvisioned = “1″
The virtual machine is now ready for power on. Verify your changes before starting the virtual machine.
Comments Off
esXpress is a very good backup system for backing up VMware ESX virtual machines. The backup appliances keeps track of you backups. If wipe your backup directory you will need to wipe the database also in the De-Duplication appliance. Or if your De-Duplication appliance gets messed you need to re-import the backup information here is how.
In order to begin, please ssh or console into your DeDupe appliance as root. To clear the appliances internal database. The following command will do just that:
phdd_wipe –db –force
To Import
phdd_import –reimport
This works in version 4.x of PHD Backup
Comments Off
It is very easy for convert from Thick disk to Thin. I am not sure which versions this works on so please check if you are using anything before ver 4.x.In the console…
vmkfstools -i /vmfs/volumes/esx01local2/Folderofthevm/vmdiskname.vmdk /vmfs/volumes/esx01local2/Folderofthevm/vmdisknameThin.vmdk -d ‘thin’ -a lsilogic
If you have spaces in your path make sure and enclose them with single quote marks like this…
vmkfstools -i ‘/vmfs/volumes/esx01local2/Folder of the vm/vmdiskname.vmdk’ ‘/vmfs/volumes/esx01local2/Folder of the vm/vmdisknameThin.vmdk’ -d ‘thin’ -a lsilogic
Comments Off
