Here in Europe the big mobile Telco’s are being forced to keep roaming prices down. But going abroad with all your data services turned on can mean you might come back to a big bill.
Solution
1. On most peoples phones “Data Roaming” is already disabled (Mines always off).Data Roaming is designed to let you use another provider’s phone network if your carrier signal is too weak. On some sites it says you cant use your phone abroad if you have this disabled I DISAGREE, I’ve got it disabled and I use my phone every time I’m out of the country?
Settings > General > Network > Data Roaming.
2. If you see ActiveSync and/or have mail pushed to your phone, you might want to also disable “Mobile Data” to stop that happening while your away.
Settings > General > Network > Mobile Data.
3. That’s Data stopped but your phone will still function as a phone. WARNING you may still be charged “call forwarding” if your phone rings and you let it go to answer phone while you are away. I don’t mind that, because I prefer to keep my phone on. If you want to disable the phone and text features as well, e.g. You Just want to use the Camera, iPod, and Alarm capabilities. Then just put the phone in Airplane mode, (which isn’t a word Apple! The word is Aeroplane!)
Settings > Airplane Mode.
Related Articles, References, Credits, or External Links
If your VC Database reaches 4GB, the VMware Virtual Centre Server service will stop. A restart of it will result in the service stopping again within a minute.
You will also see see this event logged.
Description:
Could not allocate space for object ‘dbo.VPX_HOST_VM_CONFIG_OPTION’.’PK_VPX_HOST_VM_CONFIG_OPTION’ in database ‘VIM_VCDB’ because the ‘PRIMARY’ filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the file group.
Last week a client rang in to say their servers system drive was running out of room. A quick scan showed me the biggest thing on there was a 12 GB database called SUSDB.mdf.
A few searches told me what I’d already guessed from the name, WSUS was the offender, so I set about moving it to their data drive that had lots of free space.
Solution
1. Launch the Windows SBS Console > Backup and Server Storage > Server Storage > Move Windows Update Repository Data.
2. If you are using third party backup software you may see this warning > OK.
3. Locate the Drive you want to Migrate TO and select it > Next.
4. This will move a few GB of data across to the new location. However it does NOT move the database itself.
5. To actually move the Database > Start > All Programs > Microsoft SQL Server 2005 > SQL server Management Studio Express, (Note: You may need to run as administrator).
6. Change the server name to the following and log in.
[box].pipeMSSQL$MICROSOFT##SSEEsqlquery[/box]
7. Expand Databases > Locate the SUSDB Database > Right Click > Detach.
8. Tick the “Drop Connections” box > OK.
9. I suggest you COPY the database from the system drive to the new drive.
10. Once its moved across, back in the SQL management studio > Right click Databases > attach.
11. Add.
12. Browse to the NEW location of the SUSDB.mdf file > OK.
13. OK.
14. Once the database is successfully added back in you can go back to the system drive and delete the original WSUS database.
15. When finished, it’s good practice to tidy up the database > From within the Window Server Update Services Console > Options > Server Cleanup Wizard.
16. Select All > Next > Prepare to wait A LONG TIME (this will probably take a few hours!)
17. When its finished you should see something like this.
Related Articles, References, Credits, or External Links
I don’t have many clients left that still have Exchange 2003, so this will probably be the last time I have to do this (famous last words).
Exchange databases NEVER get smaller, if you delete information out of them, it simply creates white space, that Exchange will reuse, (so they will steadily grow in size). Before you carry out this procedure, get your users to clear down their mailbox’s. Also delete/purge any unused mailboxes, this will make your defrag more efficient.
Solution
In my case the server the database was on was short on drive space. Remember you need 110% of the size of the database free space to carry out this procedure (so a 50GB database needs 110GB of free space to defragment). I did this with an external USB Drive.
Note: Moving large databases to USB media can take a while, at USB 2 Speed (48MBps (480Mbps)) took about 45 minutes to copy the database files to it.
1. You don’t need to to do this but, locate where the log files for this database are being stored, because in a minute we are going to take a copy (just in case). Right click the storage group the database is in > Properties > General > Transaction log location.
2. Now for the database itself, right click the Mailbox Store (or public folder database if that’s the one you are going to defrag) > Properties > Database > Exchange databases.
3. On my external drive I’ve created two folders, one holds the original untouched database files and the logs, the other (EDB_Files) holds a copy of the priv1.edb and priv1.stm files for the mailbox database that I’m going to defragment.
4. Eseutil.exe lives in the Exchange program folder in the bin directory, change to that directory;
[box]
cd “c:Program FilesExchsrvrbin”
[/box]
Now if we simply run eseutil on the database, it will create a temporary database on the C: drive, which I don’t want (remember we are tight for drive space). So I will specify where the temp database will be, and start the defragmentation.
[box]
eseutil /d {Path to the Database} /t {Path to the temp Database}
e.g.
eseutil /d H:EDB_Filespriv1.edb /t H:EDB_FilesTempDB.edb
[/box]
How long will eseutil take? That’s a horrible question to answer, it depends on the CPU/memory of the server, and the size of the database itself. in this case it was a 70GB Database, on an HP G4 Series server, it took 11 hours and 6 minutes (approx).
5. When done it should say it has completed successfully.
6. You can now delete the original EDB and STM files from the Exchange Server.
7. Then copy and paste your defragmented versions back into the original folder.
8. You can now mount the mail store(s).
9. Finally make sure you get a full backup of the Exchange database, (with some Exchange aware backup software).
Related Articles, References, Credits, or External Links
