Windows Servers

How do I start a backup on backup exec for windows servers?


Hi, Please refer the Admin guide for Backup Exec 11d http://support.veritas.com/docs/288005 dev

Anybody know a glitched username in Windows Based Servers?
Well.. I recently had a Novell based server but they switched it to Windows. I had found a glitched up username that gave me an administrator account and I would like that again... Can anybody help?

What? If there was a bad username added that gave you admin rights, it was probably just bad IT maintenance, not a glitch in Novell.

how to start my servers with windows login or start up?
i want to start 3 servers when windows startup,in that case server1,server2,server3 start in sequencely that is server2 wait for server1 and server3 wait for server2.. wat is solution?

manually turn them on.

How do I find out my Stanground College incoming and outgoing servers in windows outlook?
I'm in year 7 and i'm trying to set up my school email address in Windows outlook but I don't know what my incoming/outgoing server is. Can somebody help me please? Thnx

if your email address is ????@something.com, then try these: outgoing: mail.something.com or smtp.something.com Incoming: mail.something.com or pop.something.com

How many technicians do I need to support 25 Windows Servers?


You could do it with only one if he/she is a MCSE and if their only responsibility is maintaining E-Mail, Web, File, etc. If you expect them to maintain user accounts, policies and the like - better to have 1 senior technician and a couple of juniors and interns.

What is the newest or upcoming Operating System(OS) for Windows Servers?
I'm just wondering because I am too lazy to check myself.

they've had vista for agood what is it 6 months? it sucks for gaming. takes toooooo much RAM and is a memory hog. they haven't announced a new one, i dont think

What are the limitations of the current file system used by Windows Servers?


The following are a few limitations of the NTFS file system. Reserved File Names Though the file system supports paths up to ca. 32,000 Unicode characters with each path component (directory or filename) up to 255 characters long, certain names are unusable, since NTFS stores its metadata in regular (albeit hidden and for the most part inaccessible) files; accordingly, user files cannot use these names. These files are all in the root directory of a volume (and are reserved only for that directory). The names are: $Mft, $MftMirr, $LogFile, $Volume, $AttrDef, . (dot), $Bitmap, $Boot, $BadClus, $Secure, $Upcase, and $Extend [10]; . and $Extend are both directories, the others are files. Maximum Volume Size In theory, the maximum NTFS volume size is 264-1 clusters. However, the maximum NTFS volume size as implemented in Windows XP Professional is 232-1 clusters. For example, using 64 KiB clusters, the maximum NTFS volume size is 256 TiB minus 64 KiB. Using the default cluster size of 4 KiB, the maximum NTFS volume size is 16 TiB minus 4 KiB. Because partition tables on master boot record (MBR) disks only support partition sizes up to 2 TiB, you must use dynamic volumes to create NTFS volumes over 2 TiB. Maximum File Size Theory: 16 EiB minus 1 KiB (264 bytes minus 1 KiB). Implementation: 16 TiB minus 64 KiB (244 bytes minus 64 KiB) Alternate Data Streams Care must be exercised when copying or moving files from NTFS to other filesystem types. Windows system calls and programs can have varying behavior with regard to alternate data streams and might silently strip those which could not be stored on the destination filesystem. A safe way of copying or moving files is to use the BackupRead and BackupWrite system calls, which allow to enumerate streams, to verify whether each stream could be written to the destination volume and to knowingly skip offending streams.

What is the difference between Windows and Linux Servers?
In not too technical terms - what is the difference between thse two? If I were to use .net nuke , is there a perference over which server I should use?

Wow! This is a question that pops up all over the web, and one that I had myself as a web services person. You can read a lot about the differences - as well as the advantages of one over the other. In the sources area, I've listed several such discussions and articles, including the last item which is a lengthy discussion in a Wikipedia article on the subject. In terms of finding something non-technical, I would recommend the first site. The article from AskWebHosting.com states the following about using .net: "If you intend to create your site using ASP, FrontPage, the .NET environment, Windows Streaming Media, Access, MSSQL, or any of the other Microsoft proprietary technologies then you probably need to use a Windows host. There is limited support for a number of these technologies in Linux, but they can be expensive and are usually lacking in features." But you're talking about using DotNetNuke, which is an open source answer to .NET. As such, it may not matter at all, from that standpoint, which option you choose. I hope that these sources are helpful! Librarians--Ask Us, We Answer! This question was answered by Sarah Houghton-Jan, Web Services Librarian at California’s San Mateo County Library (www.smcl.org). To get instant-answers, contact your local library. Find yours at http://lists.webjunction.org/libweb/Public_main.html. Many library websites offer live browser-based chat reference 24/7 (http://liswiki.org/wiki/List_of_libraries_providing_virtual_reference_services) and/or instant messaging chat reference (http://www.libsuccess.org/index.php?title=Libraries_Using_IM_Reference).

What are the pros/cons of moving to UNIX file servers from Windows file servers?
We are considering moving to a UNIX solution for our file-servers in an environment where all workstations are Windows machines. I'm assuming we'd be using Samba for this, but was curious what are the long and short term benefits/disadvantages of doing this?

Pro : Unix is usually faster than windows. Con: You'll have to be sure file names have no spaces.

How does the hardware requirements for Caldera, SuSE, and Red Hat compare with windows servers 2003?


Roughly the same; it depends on what you intend to use the server for. That is, if you are going to be building a system that is just serving up files, you'll want good and fast disk access and throughputs regardless of the operating system. If your servers are going to be doing a lot of processing of data, you will want to have some beefy processors, and probably several of them. In most cases, you'll want to have a good bit of RAM to handle the multiple requests servers tend to get. In other words, it matters less what operating system you're going to use and more what you're going to DO with your server in picking out your server hardware. Now, that said, the one exception to that rule is in hardware support; not all manufacturers have Linux drivers, for instance. (I'm wrestling with a PC that has a Broadcom wireless chipset with Fedora, but it requires a proprietary firmware and so I have been presented with some odd issues there). If you intend to use Linux of any flavor, make sure the hardware has support under Linux. To get to the heart of your question a bit more, just as you need to look at what your server will do to determine the hardware requirements, you need to look at what you want it to do in order to determine the o/s requirements. Do you want an Active Directory domain controller? Win2003 is the hands down winner. (Obviously.) Want to do something else? Figure out which O/S does it best, go from there. :) Hope this helps!