Hot answers tagged windows-sbs
8
You can't create a trust relation with an SBS server domain and another, existing domain.
We migrated from SBS2003 to individual Server 2003 and Exchange 2003 servers for this reason. We found that the migration path is weakly supported by MS, and I was worried to death that it wouldn't work. We invested in a pack from www.sbsmigration.com to help us ...
6
You need to grant the users the "Send As" permissions. Not sure how to accomplish that on SBS 2003, but on Exchange 2003 you will:
Start the Exchange version of Active Directory Users and Computers
From the View menu choose Advanced Features.
Right click the user who wants to let other people send messages on his behalf and select Properties.
Select the ...
6
As much as I hate to say it, but if all the desktops are windows, I'd say you need windows SBS. Very easy and straightforward to install and set up for a SOHO.
If you ave the time, and especially the knowledge, sure, you can install Linux (why Ubuntu when there's Debian and CentOS available escapes me, but it's your choice). It will do everything you need, ...
6
It would generally refer to the practice of running a Type 2 hypervisor on top of Windows, with some kind of Virtual Machine running inside.
An example would be VMWare Workstation. You install the VMWare Workstation software onto Windows and then, within that, VMWare simulates another machine. For example, you may be running Windows 7 but choose to install ...
5
It's not possible. If you give someone Domain Admin, anything that you put in place can be skirted.
If you don't want this new admin to have unchecked powers right away, then you'll need to take him out of the Domain Admins group. You can make a new group and delegate only what you want him to be able to do to that new group. The Delegation Wizard in ADUC ...
5
SBS includes Sharepoint (Windows Sharepoint Services - WSS) which can do basic document sharing over HTTP.
More info from TechNet:
http://technet.microsoft.com/en-us/windowsserver/sharepoint/bb684453
5
Have you tried using the following registry value? This usually works with integrated authentication (not basic/forms authentication).
Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters
Value: AuthForwardServerList
Type: Multi-string
Refer to the following document for more information:
Prompt for Credentials When ...
5
You're looking at residential connections. Remember, you can often get Comcast business internet with a better service level agreement and different terms of service.
Personally, there's nothing wrong with getting an unmanaged dedicated server or VPS somewhere remote via a respectable web hosting company.
5
If your email and other needs are met elsewhere then you might like to look Windows Server 2008 R2 Foundation edition. This allows up to 15 users.
It can act as a domain controller as long as it is attached to the domain root (presumably to stop larger enterprises using Foundation edition as departmental servers attached to the enterprise domain). While ...
5
Due to the fact the company only has 10 employees and doesn't need anything drastic, I'd recommend Microsoft SBS 2011 (Microsoft Small Business Server 2011). This would easily be able to cope with your needs, it's easy to manage and can hold up to 75 users if you go for the "Standard" edition or 25 if you go for the "Essentials" edition.
Regarding ...
5
If you go to your Active Directory Users and Computers console (under Administrative Tools), you should be able to select multiple users inside a single OU and delete them all at once:
This should make it a lot quicker.
(that screenshot was taken on an SBS2011 machine, but it's pretty much the same on 2003).
5
First of all, SCE is overkill for 5-6 desktop machines. WSUS is probably a better option and is free.
You haven't said much about what exactly has failed. Was it a part in the machine? Is this a dusty environment? My primary support environment is approximately 40 users with approximately 10 servers (not including virtualized). We buy Dell machines ...
4
Really, just hang in the community of SysAdmins and let the goodness rub off and the badness roll off. Read blogs, hang on forums, don't be afraid to ask questions and let the flames burn the dross off (should any come your way... which I hope not).
I'll give you some pointers to groups and resources I like:
SysAdmin Network (A little slow, but there are ...
4
As far as I'm aware you cannot have trust relationships with SBS 2003, which would have been useful here. If you don't mind spending some pennies then you could purchase the SBS 2003 transition pack which will migrate the SBS 2003 domain to a Windows 2003 domain. More info can be found here
4
Sounds like a pretty straightforward deployment.
It sounds like you've already created your domain. Since you're using SBS, be aware that the existing SBS machine will be forced to hold all the Active Directory flexible single-master roles. That's probably not a big deal, but the 75 user limit in SBS might be. While SBS makes for an attractive price-point ...
4
Starting from the outside in.
DNS
Active Directory will need Dynamic DNS of some kind. If your existing DNS servers can't do that, then you'll need to use different DNS servers for just the AD domain itself. This is actually a pretty common config. The DNS domain used by Active Directory is something else than where you receive your mail (example: if you're ...
4
Sam beat me to this, as his answer came whilst I was typing mine. As Sam recommended, I will point you to the transition pack, from Microsoft. This knowledge article can also be very helpful, as well as this post, from which I quote one entry:
Install Windows 2003 on a new computer.
Setup TCP/IP using static IP and DNS pointing to the SBS DNS.
...
4
Are you running an Open Relay? If not then I believe you do have a virus. It's time to find the culprit, do that fast otherwise you'll get your domain blacklisted. Something like this happened to me a long time ago and it was I was running an open relay.
Run this site to see if you're running an Open Relay: http://www.checkor.com/
Check this thread for ...
4
Try to identify if the MAC address belongs to any equipment on your network. You can lookup vendor addresses here.
Do you have a wireless access point on your network, is it secured? look for the MAC addresses of any connected devices. You can normally view these from the access point.
Do you have any virtual machines running on any of the workstations or ...
4
The forwarding options on a mailbox enabled user don't allow for forwarding to multiple recipients (that I'm aware of) so my guess, based on the fact that two users are listed in the recipient field, is that this is actually a ditribution group. Have you verified that Customer Service is a user mailbox and not a Distibution Group?
Try creating a custom ...
3
It sounds like backscatter (NDR spam) to me, rather than your server being an open relay. Exchange Server 2003 by default is not an open relay. You can check whether or not your Exchange server is an open relay by using any number of online tests. You can help prevent backscatter spam in a few ways:
Disable NDR's on your Exchange server.
Filter email sent ...
3
Group Policy may not have refreshed yet. It is not an instantaneous process, the clients have to actually check for new policies, which happens at an interval that is defined in the Default Domain Policy.
Even if the interval period has passed, some settings are not applied until the computer starts up, or a user logs in. You can check the policies that ...
3
You don't want to disable that service in Windows Small Business Server 2003 (SBS) per Microsoft. In some versions of SBS the server computer would STOP after a period of time with a SYSTEM_LICENSE_VIOLATION if you stopped that service. Be glad your box isn't doing that and leave the service alone.
3
You'll want to ensure that your existing Active Directory and Exchange environment is already healthy. If it's not, definitely clean that up before any migration. You're on the right track with everything else. Transfer DHCP to the new server once it's a member and a domain controller. Installing and migrating Exchange isn't something that you'll be doing, ...
3
There isn't really much point in running SBS without Exchange, but you have spent the money already so you might as well use the license. AFAIK it['s perfectly save to uninstall Exchange, however, I would not waste any time on that. I would simply disable all Exchange related services and get on with whatever else needs doing.
3
There are basically two reasons not to run SBS.
You need more than 75 licenses (total of user + device CALs).
You need to run a line-of-business application that explicitly doesn't support SBS (these are quite rare, so its unlikely to be a problem).
Aside from that, I cannot think of any compelling reason not to run SBS. There is a restriction of a ...
3
The problem you're going to run into is that Active Directory uses DNS to tell client machines where to find various resources, so turning off DNS on the Windows server will eventually stop things that require Active Directory from working. It sounds like it worked for a number of hours because clients had it cached, but then the cache expired.
My ...
3
Windows Server 2012 Essentials is the replacement for the Windows Small Business Server product line and does not include any entitlement to use Exchange. Quoting Microsoft's Windows Server 2012 Essentials Benefits document:
In previous versions, Windows Small Business Server Standard included
Exchange Server as a component product, which added expense ...
2
The hypervisor to use is largely a matter of personal preference. It may be in your interests to go for a Hyper-V host using Windows Server 2012 Standard - the virtualisation rights now included for a particular number of VMs (and unlimited in the Datacentre edition, I do believe) can now make this pretty cost effective.
At a high level, you are looking at ...
2
Check to see if you're using a smarthost. This can be configured in 2 places in Exchange 2003:
SMTP Virtual Server - Administrative groups -> administrative group name -> Servers -> server name -> Protocols -> SMTP -> Right click on default SMTP virtual server, go to properties -> Delivery tab -> Advanced. Check the smarthost entry
The connector - ...
Only top voted, non community-wiki answers of a minimum length are eligible
