jinnantonnixx

I hear you bro. This is one of my favourite articles, I've posted it before so apologies if you find my fantastic links irritating. http://www.nikhef.nl/pub/services/biblio/bib_KR/sciam14327034.pdf P.S. I've got spare tickets for this place - anyone fancy coming along? Genesis Expo - Creation Museum in Portsmouth

The Sansa Clip is excellent. Cheap, sounds good, very light and has a clip for attaching to sleeves or whatever. It's drag and drop (both ways) across Windows, Linux and Macs.

I forgot all about the discount at Orange. Was the phone unlocked? Have Orange added any nonsense to it?

I had to open the thread to check too! Matt goes postal. Well anyway, it's got to be Powershell all the way for this task. This will get you off to a flying start. Top 10 Active Directory Tasks Solved with PowerShell | PowerShell content from Windows IT Pro Managing AD in Bulk Using PowerShell | Active Directory content from Windows IT Pro

True enough, The scripts look a better bet.

From your SQL server, run a command prompt then type SQLCMD -L That will list all instances it finds on the network. If you're just interested in a particular server, SQLCMD -L | FIND /I "your_server_name" and to just count instances SQLCMD -L | FIND /I /C "your_server_name"

Also, are you mapping via the advertised share e.g. f:\ = \\server\someshare Try mapping directly to your hidden disk share net use f: \\127.0.0.1\d$

Try a SUBST rather than a map, see if the error persists. Subst - Substitute a drive letter for a network path. | SS64.com e.g. subst f: d:

Much as I hate Powershell, I think it will be the preferred method for what you want to do. Powershell - Adding computers to a security group in Active Directory - Stack Overflow Of course you will need the correct security to do this, but you can run this yourself with nothing more than a list of the computers and the one line of Powershell. To view the group memberships of computers, Powershell is useful. get-adcomputer -filter 'name -eq "name_of_computer"' -Properties memberof You can use wildcards get-adcomputer -filter 'name -like "science*"' -Properties memberof

Yes, the scheduled task can be a VBS, but you must call it using the full path of the script interpreter (usually cscript) Explained here. vbscript - can .vbs file be a scheduled script? - Stack Overflow

You could store your scripts in a scheduled task with the appropriate security credentials, but scheduled to never run (stay with me...) Then, when you need to, use the "schtasks /run /tn TaskName " command to run the script on demand. How to use Schtasks.exe to Schedule Tasks in Windows Server 2003

Have you changed any BIOS settings to high performance? If so, restore settings to default. Try booting into Knoppix (cd or usb) and see if the problem happens. Knoppix won't affect anything on your system. This will rule in/out Windows device/display drivers, etc. Knoppix Linux Boot CD, Download Disk and Documents, Discuss, Get Help Download here http://www.mirrorservice.org/sites/ftp.uni-kl.de/pub/linux/knoppix/KNOPPIX_V7.0.5CD-2012-12-21-EN.iso

Ah. Are you running it as a particular user with the correct permissions in Task Manager? Get back to basics, change the code to direct errors to a file to see if that helps net use > wtf.txt net use Y: "\\[server]\[share]" >> wtf.txt

You should specify a full path for the log.txt file. When it's running as a schedule, unless you specify the 'start in' path, it has no relative location for log.txt. You can understand its confusion - where on earth should log.txt live? Even if you use the 'start in' option, it's always better for specify full paths in all scripts. I'm mostly Linux these days, but if my DOS memory is still working, you might want to try something like this to give you more flexibility if you need to change/rename the log file. SET LOGFILE=c:\someplace\log.txt .... echo 'stuff I want' >> $LOGFILE

Good site. Let's just say the Vietnam war ended when I was a child, but at least I didn't start it.

Anonymous prankster replaces wine bottle labels at tesco in brixton south london with hilarious self-made labels that say things like great with roadkill | Metro News

Coffee amongst geeks is not to be taken lightly. Here are some interesting articles I found. The science behind the perfect coffee It turns out that hard water makes better coffee. First scientific method to authenticate world's costliest coffee

I use Sundroid on my phone - it has an identical feature. Sundroid | Apps | Visalia Mobile

I present unto thee the ZX Spectrum Master Class in Programming.

Terrible puns, and that's being Magnuminous. I'm desserting this thread.

Yeah, practice practice practice. When you've got it down pat. print out instructions ON PAPER (not left on the root folder of the server which has crashed) and TAPE THEM TO THE WALL not mixed in a pile of magazines next to the bin. Bitter experience is a harsh tutor.

I had to script my setup, so that was tricky, I grant you. But don't be worried, if you only have a couple of databases, the Log Shipping wizard thing sorts it out for you. It's OK. Here's a guide that shows you the wizard. Step By Step SQL Server Log Shipping Don't test the water with both feet, test it on a dummy copy of the data or better still in a virtual environment. Make sure you can restore and change-over, this either means changing the database name or point SIMS to the new database (don't forget to restructure the Docstorage folder structure). Do it again and again, until you know it inside out and you're sure you can get a working restore under pressure.

If you use log-shipping, do not combine it with any other transaction backup routine on your database (i.e. something else that backs up the logs files). Every transactional backup will truncate your logs. If you're using two backup systems (log shipping + something else), each of these will truncate the logs. The result will be a useless and broken log-shipping system and a useless and broken backup system. Not an ideal situation. Your heart sinks when you see a broken LSN chain. If you need to make ad-hoc backups/copies of data, be sure to use the COPY ONLY flag on the backup. This feature doesn't touch the logs. It's fine to do, say, full backups at night or at the weekend (full backups don't truncate the logs), but don't mix and match log/transactional backups with log-shipping.

I would always keep the OS and data as a separate concern. Sometimes a OS can go disastrously wrong, but your data is OK. Restoring an SQL server as an atomic entity would mean that you'd lose data if you needed to restore to a previously working version of the OS. If the OS and data are on different disks (as they should be!) then the database can be remounted on a new OS quite easily, so this is a reasonable strategy.

Gah! I scream at the idiocy of this.