Teknologisk videncenter - User contributions [en]

User:Trillex

2014-01-16T17:20:46Z

Trillex:

Smart mand.
== Smarthed ==
Jeg ved noget I ikke ved.

Trillex small business server 2008

2009-09-25T07:37:26Z

Trillex: /* IP Table */

= Deployment of Small Business Server 2008 =

== Introduction ==

For this week, I am going to deploy a Small Business Server 2008, that would be suitable for a "standard" business.

Just to give me some kind of aim, I will put up these demands for myself:

The company has 15 computers. They require logins which go through an exchange server. As any normal company, they also require emails, a website, personal login and a means of getting their files stored remotely on the server. A VPN connection for the workers as well as a means to manage the server remotely could also be mandatory.

=== Introduction to 64 bit Architecture ===

With Windows Server 2008, Microsoft made their operating system 64 bit. This is done for several reasons, but the "main" reason is that it supports more than 4 GB of memory. They've actually made it mandatory, so you cannot install it without less.

There are more to it, but mostly in memory allocations i.e. larger address spaces, wider registers and data paths. If a 64 bit operating system is handling a 64 bit compiled program or game, it will feel faster in that it got less limitations. This means that the processor can process more data at a time.

== Small Business Server 2008 ==

Microsoft have developed this branch of server operating systems to benefit smaller business that do not require big servers. By doing this, they've made a cheaper license that most business can afford with the ability to update.

=== Features and Components ===

*E-mail Server Application (Through Exchange).
*IIS Server Application. This is essentially a webserver.
*DHCP server
*DNS server
*Active Directory for handling Users and Groups
*Remote Web Workplace, Remote Desktop and VPN support
*Firewall
*Virus Scanner in the form of OneCare.

=== Limitations and Requirements ===

Windows Small Business Server 2008 has certain restrictions. This is because Microsoft wanted this to fit, as the name says, a small business so they put in some limitations to make the server operating system cheaper. Most business will not be affected by these limitations. A lot of the limitations, like a specific amount of space for emails, can be managed by implanting business policies - such as making sure you keep a tidy email account.

These limitations are:

*Only one SBS server in a domain. The domain can only handle more servers if these are of a different operating system, i.e. like linux, Windows Server etc.
*SBS is very picky about domains. It can only handle one and no child domains.
*Must be the root of the Active Directory forest.
*It is limited to 75 users (licenses).
*Earlier versions of SBS were limited to max 4 GB of memory. SBS 2008 requires a minimum of 4 GB and got a maximum limited of 32 GB. This is due to earlier versions being based on the x86 (32 bit) architecture while 2008 is based on x86-64 (64 bit). This change is because of Exchange Server 2007 is running in 64 bit.
*There are two different versions of SBS 2008. Standard Edition and Premium Edition. The difference between the two are: Premium includes a license to another Windows Server as well as MSSQL database.
*I am not certain if this limitation is still active in 2008 - but in Small Business Server 2003 service pack 2, the Exchange server limits you to 75 GB of emails.

If the business suddenly hits one of these limitations and needs to grow even further, it is possible to upgrade to a bigger license.

=== Installation of Small Server Business 2008 ===

Everybody knows how to press next and fill it out. So I will only fill this out with information that deems necessary to this project.

==== Partitioning ====

Normally, a server will have several harddrives in it and will run a certain kind of raid. Some people like to partition their harddrives to make it more "manageable" because they can assign certain drive letters to specific things, like documents for users etc. This is not at all necessary but can be easier to mange for certain people. I have decided not to do it - simply because it is not needed. By doing it this way, you will also force yourself to "read" drive/folder layouts and optimize them properly. This might be a linux thing but I prefer it this way.

In short, it's a matter of preference.

==== Updating and Virus Protection ====

Throughout the installation, it asks us whether or not we want to keep it up to date with updates and install it's virus scanner. We might as well, eh? Don't do it if you plan on using another one.

==== Post-installation ====

For the love of everything, remove UAC at once. It will make you hate everyone. Do that now.

=== Setting it Up ===

==== Internet Connectivity ====

An important part of a good business network, is having a constant connection to the Internet.

As we do not have a server with two ethernet interfaces, we are forced to do it a different way.

I believe that the best way to do it, is to let the router do the "sharing" and make the server give the IP, gateway and DNS information through it's DHCP server with a standard scope.

As I cannot do this with the current setup, I will not attempt it.

==== Adding Computers to the Domain ====

A pretty nice change in SBS is the ability to add computers. Not only does it add a computer, but it also installs certain tools to make sure that you can monitor a computer without having to physically look at it, i.e. it monitors virus scanner, status, updates etc and gives you a means to log on to it if needed. The way to do this is:

#Have a ready made XP installation. Login as Administrator.
#Go into a webbrowser and go to http://connect - or plug in a USB drive and tell the server to put the necessary files on there
#Follow the simple wizard.

==== Easy Configuration ====

Small Server Business 2008 has taken a hint from the unix world, and have truly made it a lot easier to manage users and set up the system. Upon installation, it starts up and installs the most commonly used services and utilities, such as DNS, IIS, Active Directory and more (these are also called roles and features). But the Windows SBS Console also allows for some amazing wizard options. If you want to add a user, it will automatically create a personal share for it, set the permissions for that folder as well as a "global" shared folder, create an email and send them a default "Welcome" email. Along with this, it can also print out this information. It is sort of a default way to do it, which can be very limiting to some.

While certainly streamlining the general process of managing and monitoring the server and the network, it can get very limiting in certain aspects and if you want to do something that isn't in the SBS Console, you will have to dig it out. If you are not familiar with earlier versions of SBS or Windows Server in general, you could get into a lot of problems doing something that was meant to be easy - like changing DHCP scope options, advanced permissions and logon scripts.

===== Shares =====

As stated above, the installation puts up a very standard, yet functional means of managing and taking care of shares. This is all very good but can be tedious to have to redo, since it just puts it in a standard folder called C:\Users\. If you have several partitions or harddrives, you'd most likely want to make use of them for user shares and documents. Thankfully, it is relatively easy to delete and redo the shares on different folders and is conveniently described in the SBS Console.

It is also with relative ease that you can ensure that only certain users can enter certain directories/shares. It is done in the same way as most 2000+ Windows operating system - but I will just scratch it down quickly; You can do it the time consuming way or you can just add groups that certain people have access to. This is all done through the standard Active Directory or can be done through the SBS Console.

I'd personally recommend keeping the sharing structure this way. There aren't many situations where you'd need to create it in a different way. So don't fix what isn't broken.

===== Users =====

As I noted earlier, there are several means of grouping people, so mundane tasks are quickly done - like sending an email to a group of people can easily be done by putting them into a so called "Distribution Group". This creates the group on the email server and when mails are sent to this group, every one who is a member, will receive an email. Good for announcements.

You can also group people in security means which, surprisingly, is called "Security Groups". Using these security groups can be wise if you only want a specific amount of people being able to use, say, a printer or a cetain share. You can, for example, have a group just for the big bosses where they are given access to just about everything.

Both of these groups can be attached to users during addition of users and groups.

=== Tools of Small Server Business 2008 ===

Microsoft have expanded a bit on their tools from 2003, most notably Windows SBS Console and Server Manager.

There are 2 different version of Windows SBS Console, normal and advanced mode - though all that advanced does, is add a few extra features under "Tasks".

These two tools cannot really be compared as they are governing two different aspects of the server. While Windows SBS Console is more monitoring, adding of users, shares etc - which is more like every day stuff - the Server Manager is exactly what is said in the name. It manages the server and keeps logs of everything running in the background. Essentially, it is a glorified Event Log as well as a Add/Remove Windows Components - just a lot more advanced in it's features.

Through Server Manager, you can add, remove, start, stop, restart and configure most "roles". Microsoft now call the background things going, i.e. like DNS, DHCP servers "roles". Which makes sense. The things on the frontend of it all, is then called features. These features include tools of varying kind - i.e. for deeper management of every specific role. For example, there are the role called DNS Server and for it, there is a feature called DNS Server Tools. It also has the ability to add "role services" which is essentially a module that can be added to a specific role. An example is that File Services can have a role service called Windows Search Service.

As stated earlier, it is also a event viewer. It keeps track of just about everything that is going on and lists if there has been an error on a specific role or if something has gone horribly wrong - much like what the SBS Console does, except this is deeper - it will show a warning symbol or something else in the main panel and then you can start digging into it.

Obviously, you can find and configure more in details if you go directly to the role/service itself than if you went through SBS Console or Server Manager. Both of them, however, conveniently link to this. A thing to note, is that whatever you add through SBS Console will be added to Active Directory, i.e. users and groups added will be added in it. If you view through Active Directory, you will see these in it's own directory, so you can sort through what changes came from SBS Console.

I am really loving these extra tools, that just make server monitoring, and to some extent, managing a server a lot easier. Just having a monitor attached to it with SBS Console running constantly will make sure that a lot of errors are caught early on.

=== Remote Web Workplace ===

Again, a great feature from Small Server Business - The Remote Web Workplace is just what it says - a means to connect to work from home and have access to just about everything you need. Intranet website, e-mail and Remote Desktop Connection to any computer you are allowed to. Great for those who wants to clock in some extra hours from home. You can even expand it with Office AnyWhere which provides an online means of viewing, writing and using documents online.

To me, this makes VPN kind of obsolete unless you have a database tool or something that requires you to be connected to a VPN - but that could just as possible be done through Remote Desktop Connection. They still allow for VPN connection but it isn't as simple as with SBS 2003, that even allowed an easy application to be downloaded and used, streamlining the process for workers.

=== Windows Firewall ===

Firewall is, like all the other tools, preinstalled and setup. Firewall in SBS is very tightly integrated with the rest of the systems, which makes sure that the tools that need to go out, gets out and the things that need to go in, goes in.

Obviously, it got a deeper configuration, which can be accessed through the Server Manager tool.
Personally, I feel that this is the way a Firewall should be. When everything that is necessary to make a server/network run is already plotted in, you can just make minor changes and tweaks here and there for whatever you need to make use of.

=== SharePoint ===

SharePoint is a flexible "tool" from Microsoft. Essentially, it is a means to make webpages with ease using a preset form but it is more than that. It can be used as a sort of a file server or a "whiteboard" for work projects, groups and more where the workers can share their work, information etc. It is also a platform for various programs.

As an administrator, you must think it could be hell administering all of the SharePoint items that your business will make use of, but with most things Microsoft, you have a means to give other users group "leadership", so they can add/remove items themselves and generally configure their own item without having to contact their local administrator.

Through SharePoint, users or administrators can create "items" which can contain certain information or a workplan - making it an ideal platform to gather on and keep everybody up to date and synced.

A bit of a downside to SharePoint is that every site you make will, by default, make use of a new port. This means extra adminstration because you have to open up another port, depending if you are using a router or not, for every site you make.

== Network Diagram ==

This network diagram is suited for a very standard small business.

Note that since I do not have access to a computer with two ethernet interfaces, I have made it so I will not require this on the diagram. This can be a problem for certain businesses, since you cannot set up a proper firewall or monitor internet activity etc., except through a router's very limited monitoring tools and firewall. It is, however, possible.

[[Image:Sbs2008.png]]

It can be done in many ways, but this is a pretty good one for what we have available.

Remember that this is not how it will look physically.

What we got is a router that connects to the internet. We could have connected the server directly to the router and the switch with it, but that could create a necessary burden on the router - which could strain the network if huge amounts of data are passed through. You CAN do it but there is no reason to, if you already have a switch handy. Why would it do this? Well, every packet going to the server would have to go into the inbuilt switch in the router as well as every packet aiming for the web, would have to go through it. Again, you can do it but it is not ideal.

Now that we cleared that up, we have a switch connected to the router. This switch is connected to the server and as many computers as there are in the company. Notice that there easily could be more switches in the physical setup, due to computers being spread out in different departments and offices.

=== IP Table ===

{| border="1" class="wikitable"
|-
! IP
! Device
! DHCP or Static
! Gateway
! DNS
|-
| 192.168.1.1/24
| Router
| Static
| N/A
| N/A
|-
| 192.168.1.2/24
| SBS 2008 Server
| Static
| 192.168.1.1
| 192.168.1.1
|-
| 192.168.1.10-254/24
| Computers and Devices*
| DHCP
| 192.168.1.1
| 192.168.1.1
|}

<nowiki>
* Devices are network printers, IP phones and everything else that would require an IP.
</nowiki>

Pretty straightforward and easy.

=== How to Simulate at Mercantec ===

I do not have access to 15 computers or devices nor do I want to have to set up an entire Cisco Router just for this project, so I cut some corners on certain things but will still accomplish the same thing. I am only writing this here, so I can keep it organized and noted down.

<strike>After consulting Henrik about the network here, he suggested that I just use some IPs freely available here and create it out from that. These two are:</strike>

*<strike>192.168.138.128</strike>
*<strike>192.168.138.131</strike>

<strike>What I will do is give the server the first IP and the computer the second one. Because of this, I cannot install DHCP. I find that installing DHCP is pretty straight forward anyway and shouldn't need to be documented as we can just assume it is there. It is used for Internet Connectivity section and I will describe it like it is used like that. But if it is needed, let me know and I can find another way to do it.</strike>

After having tried the above, I've decided to just make a small network with just 2 computers in it with no connectivity to the internet. I enabled the scope, I described earlier and set it's gateway and DNS to the fictional router. I've updated both client and server so I shouldn't require any web access.

== Exchange Server 2007 ==

Small Server Business is using Exchange Server 2007.

Exchange Server has a lot of roles and functions that are tightly integrated into the very core of the operating system, providing one of it's main infrastructures together with Active Diectory.

Exchange major functions are that of e-mails, calendar, contacts, tasks through calendar, IIS (webserver) and data storage.

With 2007, they introduced several new features, including:

* Protection (anti-spam, antivirus etc.).
* Extensive Scripting language (Microsoft PowerShell).
* Increased allowed size of database and allowed amount of databases that can be run through Exchange.
* Outlook AnyWhere, a remote access to a web e-mail client.

== Problems I Ran Into and How to Fix ==

I started out on a different network than I was going to end up on, so my DNS had already put in all of the information required for that IP and network. This made everything a bit tricky since my client wouldn't be able to resolve anything as the DNS server is out of reach.

To fix it, I had to reinstall the role DNS server and let it reconfigure itself. Afterwards, everything worked without a hitch.

Trillex small business server 2008

2009-09-25T07:35:17Z

Trillex:

= Deployment of Small Business Server 2008 =

== Introduction ==

For this week, I am going to deploy a Small Business Server 2008, that would be suitable for a "standard" business.

Just to give me some kind of aim, I will put up these demands for myself:

The company has 15 computers. They require logins which go through an exchange server. As any normal company, they also require emails, a website, personal login and a means of getting their files stored remotely on the server. A VPN connection for the workers as well as a means to manage the server remotely could also be mandatory.

=== Introduction to 64 bit Architecture ===

With Windows Server 2008, Microsoft made their operating system 64 bit. This is done for several reasons, but the "main" reason is that it supports more than 4 GB of memory. They've actually made it mandatory, so you cannot install it without less.

There are more to it, but mostly in memory allocations i.e. larger address spaces, wider registers and data paths. If a 64 bit operating system is handling a 64 bit compiled program or game, it will feel faster in that it got less limitations. This means that the processor can process more data at a time.

== Small Business Server 2008 ==

Microsoft have developed this branch of server operating systems to benefit smaller business that do not require big servers. By doing this, they've made a cheaper license that most business can afford with the ability to update.

=== Features and Components ===

*E-mail Server Application (Through Exchange).
*IIS Server Application. This is essentially a webserver.
*DHCP server
*DNS server
*Active Directory for handling Users and Groups
*Remote Web Workplace, Remote Desktop and VPN support
*Firewall
*Virus Scanner in the form of OneCare.

=== Limitations and Requirements ===

Windows Small Business Server 2008 has certain restrictions. This is because Microsoft wanted this to fit, as the name says, a small business so they put in some limitations to make the server operating system cheaper. Most business will not be affected by these limitations. A lot of the limitations, like a specific amount of space for emails, can be managed by implanting business policies - such as making sure you keep a tidy email account.

These limitations are:

*Only one SBS server in a domain. The domain can only handle more servers if these are of a different operating system, i.e. like linux, Windows Server etc.
*SBS is very picky about domains. It can only handle one and no child domains.
*Must be the root of the Active Directory forest.
*It is limited to 75 users (licenses).
*Earlier versions of SBS were limited to max 4 GB of memory. SBS 2008 requires a minimum of 4 GB and got a maximum limited of 32 GB. This is due to earlier versions being based on the x86 (32 bit) architecture while 2008 is based on x86-64 (64 bit). This change is because of Exchange Server 2007 is running in 64 bit.
*There are two different versions of SBS 2008. Standard Edition and Premium Edition. The difference between the two are: Premium includes a license to another Windows Server as well as MSSQL database.
*I am not certain if this limitation is still active in 2008 - but in Small Business Server 2003 service pack 2, the Exchange server limits you to 75 GB of emails.

If the business suddenly hits one of these limitations and needs to grow even further, it is possible to upgrade to a bigger license.

=== Installation of Small Server Business 2008 ===

Everybody knows how to press next and fill it out. So I will only fill this out with information that deems necessary to this project.

==== Partitioning ====

Normally, a server will have several harddrives in it and will run a certain kind of raid. Some people like to partition their harddrives to make it more "manageable" because they can assign certain drive letters to specific things, like documents for users etc. This is not at all necessary but can be easier to mange for certain people. I have decided not to do it - simply because it is not needed. By doing it this way, you will also force yourself to "read" drive/folder layouts and optimize them properly. This might be a linux thing but I prefer it this way.

In short, it's a matter of preference.

==== Updating and Virus Protection ====

Throughout the installation, it asks us whether or not we want to keep it up to date with updates and install it's virus scanner. We might as well, eh? Don't do it if you plan on using another one.

==== Post-installation ====

For the love of everything, remove UAC at once. It will make you hate everyone. Do that now.

=== Setting it Up ===

==== Internet Connectivity ====

An important part of a good business network, is having a constant connection to the Internet.

As we do not have a server with two ethernet interfaces, we are forced to do it a different way.

I believe that the best way to do it, is to let the router do the "sharing" and make the server give the IP, gateway and DNS information through it's DHCP server with a standard scope.

As I cannot do this with the current setup, I will not attempt it.

==== Adding Computers to the Domain ====

A pretty nice change in SBS is the ability to add computers. Not only does it add a computer, but it also installs certain tools to make sure that you can monitor a computer without having to physically look at it, i.e. it monitors virus scanner, status, updates etc and gives you a means to log on to it if needed. The way to do this is:

#Have a ready made XP installation. Login as Administrator.
#Go into a webbrowser and go to http://connect - or plug in a USB drive and tell the server to put the necessary files on there
#Follow the simple wizard.

==== Easy Configuration ====

Small Server Business 2008 has taken a hint from the unix world, and have truly made it a lot easier to manage users and set up the system. Upon installation, it starts up and installs the most commonly used services and utilities, such as DNS, IIS, Active Directory and more (these are also called roles and features). But the Windows SBS Console also allows for some amazing wizard options. If you want to add a user, it will automatically create a personal share for it, set the permissions for that folder as well as a "global" shared folder, create an email and send them a default "Welcome" email. Along with this, it can also print out this information. It is sort of a default way to do it, which can be very limiting to some.

While certainly streamlining the general process of managing and monitoring the server and the network, it can get very limiting in certain aspects and if you want to do something that isn't in the SBS Console, you will have to dig it out. If you are not familiar with earlier versions of SBS or Windows Server in general, you could get into a lot of problems doing something that was meant to be easy - like changing DHCP scope options, advanced permissions and logon scripts.

===== Shares =====

As stated above, the installation puts up a very standard, yet functional means of managing and taking care of shares. This is all very good but can be tedious to have to redo, since it just puts it in a standard folder called C:\Users\. If you have several partitions or harddrives, you'd most likely want to make use of them for user shares and documents. Thankfully, it is relatively easy to delete and redo the shares on different folders and is conveniently described in the SBS Console.

It is also with relative ease that you can ensure that only certain users can enter certain directories/shares. It is done in the same way as most 2000+ Windows operating system - but I will just scratch it down quickly; You can do it the time consuming way or you can just add groups that certain people have access to. This is all done through the standard Active Directory or can be done through the SBS Console.

I'd personally recommend keeping the sharing structure this way. There aren't many situations where you'd need to create it in a different way. So don't fix what isn't broken.

===== Users =====

As I noted earlier, there are several means of grouping people, so mundane tasks are quickly done - like sending an email to a group of people can easily be done by putting them into a so called "Distribution Group". This creates the group on the email server and when mails are sent to this group, every one who is a member, will receive an email. Good for announcements.

You can also group people in security means which, surprisingly, is called "Security Groups". Using these security groups can be wise if you only want a specific amount of people being able to use, say, a printer or a cetain share. You can, for example, have a group just for the big bosses where they are given access to just about everything.

Both of these groups can be attached to users during addition of users and groups.

=== Tools of Small Server Business 2008 ===

Microsoft have expanded a bit on their tools from 2003, most notably Windows SBS Console and Server Manager.

There are 2 different version of Windows SBS Console, normal and advanced mode - though all that advanced does, is add a few extra features under "Tasks".

These two tools cannot really be compared as they are governing two different aspects of the server. While Windows SBS Console is more monitoring, adding of users, shares etc - which is more like every day stuff - the Server Manager is exactly what is said in the name. It manages the server and keeps logs of everything running in the background. Essentially, it is a glorified Event Log as well as a Add/Remove Windows Components - just a lot more advanced in it's features.

Through Server Manager, you can add, remove, start, stop, restart and configure most "roles". Microsoft now call the background things going, i.e. like DNS, DHCP servers "roles". Which makes sense. The things on the frontend of it all, is then called features. These features include tools of varying kind - i.e. for deeper management of every specific role. For example, there are the role called DNS Server and for it, there is a feature called DNS Server Tools. It also has the ability to add "role services" which is essentially a module that can be added to a specific role. An example is that File Services can have a role service called Windows Search Service.

As stated earlier, it is also a event viewer. It keeps track of just about everything that is going on and lists if there has been an error on a specific role or if something has gone horribly wrong - much like what the SBS Console does, except this is deeper - it will show a warning symbol or something else in the main panel and then you can start digging into it.

Obviously, you can find and configure more in details if you go directly to the role/service itself than if you went through SBS Console or Server Manager. Both of them, however, conveniently link to this. A thing to note, is that whatever you add through SBS Console will be added to Active Directory, i.e. users and groups added will be added in it. If you view through Active Directory, you will see these in it's own directory, so you can sort through what changes came from SBS Console.

I am really loving these extra tools, that just make server monitoring, and to some extent, managing a server a lot easier. Just having a monitor attached to it with SBS Console running constantly will make sure that a lot of errors are caught early on.

=== Remote Web Workplace ===

Again, a great feature from Small Server Business - The Remote Web Workplace is just what it says - a means to connect to work from home and have access to just about everything you need. Intranet website, e-mail and Remote Desktop Connection to any computer you are allowed to. Great for those who wants to clock in some extra hours from home. You can even expand it with Office AnyWhere which provides an online means of viewing, writing and using documents online.

To me, this makes VPN kind of obsolete unless you have a database tool or something that requires you to be connected to a VPN - but that could just as possible be done through Remote Desktop Connection. They still allow for VPN connection but it isn't as simple as with SBS 2003, that even allowed an easy application to be downloaded and used, streamlining the process for workers.

=== Windows Firewall ===

Firewall is, like all the other tools, preinstalled and setup. Firewall in SBS is very tightly integrated with the rest of the systems, which makes sure that the tools that need to go out, gets out and the things that need to go in, goes in.

Obviously, it got a deeper configuration, which can be accessed through the Server Manager tool.
Personally, I feel that this is the way a Firewall should be. When everything that is necessary to make a server/network run is already plotted in, you can just make minor changes and tweaks here and there for whatever you need to make use of.

=== SharePoint ===

SharePoint is a flexible "tool" from Microsoft. Essentially, it is a means to make webpages with ease using a preset form but it is more than that. It can be used as a sort of a file server or a "whiteboard" for work projects, groups and more where the workers can share their work, information etc. It is also a platform for various programs.

As an administrator, you must think it could be hell administering all of the SharePoint items that your business will make use of, but with most things Microsoft, you have a means to give other users group "leadership", so they can add/remove items themselves and generally configure their own item without having to contact their local administrator.

Through SharePoint, users or administrators can create "items" which can contain certain information or a workplan - making it an ideal platform to gather on and keep everybody up to date and synced.

A bit of a downside to SharePoint is that every site you make will, by default, make use of a new port. This means extra adminstration because you have to open up another port, depending if you are using a router or not, for every site you make.

== Network Diagram ==

This network diagram is suited for a very standard small business.

Note that since I do not have access to a computer with two ethernet interfaces, I have made it so I will not require this on the diagram. This can be a problem for certain businesses, since you cannot set up a proper firewall or monitor internet activity etc., except through a router's very limited monitoring tools and firewall. It is, however, possible.

[[Image:Sbs2008.png]]

It can be done in many ways, but this is a pretty good one for what we have available.

Remember that this is not how it will look physically.

What we got is a router that connects to the internet. We could have connected the server directly to the router and the switch with it, but that could create a necessary burden on the router - which could strain the network if huge amounts of data are passed through. You CAN do it but there is no reason to, if you already have a switch handy. Why would it do this? Well, every packet going to the server would have to go into the inbuilt switch in the router as well as every packet aiming for the web, would have to go through it. Again, you can do it but it is not ideal.

Now that we cleared that up, we have a switch connected to the router. This switch is connected to the server and as many computers as there are in the company. Notice that there easily could be more switches in the physical setup, due to computers being spread out in different departments and offices.

=== IP Table ===

{| border="1" class="wikitable"
|-
! IP
! Device
! DHCP or Static
! Gateway
! DNS
|-
| 192.168.1.1/24
| Router
| Static
|
|
|-
| 192.168.1.2/24
| SBS 2008 Server
| Static
|
|
|-
| 192.168.1.10-254/24
| Computers and Devices*
| DHCP
|
|
|}

<nowiki>
* Devices are network printers, IP phones and everything else that would require an IP.
</nowiki>

Pretty straightforward and easy.

=== How to Simulate at Mercantec ===

I do not have access to 15 computers or devices nor do I want to have to set up an entire Cisco Router just for this project, so I cut some corners on certain things but will still accomplish the same thing. I am only writing this here, so I can keep it organized and noted down.

<strike>After consulting Henrik about the network here, he suggested that I just use some IPs freely available here and create it out from that. These two are:</strike>

*<strike>192.168.138.128</strike>
*<strike>192.168.138.131</strike>

<strike>What I will do is give the server the first IP and the computer the second one. Because of this, I cannot install DHCP. I find that installing DHCP is pretty straight forward anyway and shouldn't need to be documented as we can just assume it is there. It is used for Internet Connectivity section and I will describe it like it is used like that. But if it is needed, let me know and I can find another way to do it.</strike>

After having tried the above, I've decided to just make a small network with just 2 computers in it with no connectivity to the internet. I enabled the scope, I described earlier and set it's gateway and DNS to the fictional router. I've updated both client and server so I shouldn't require any web access.

== Exchange Server 2007 ==

Small Server Business is using Exchange Server 2007.

Exchange Server has a lot of roles and functions that are tightly integrated into the very core of the operating system, providing one of it's main infrastructures together with Active Diectory.

Exchange major functions are that of e-mails, calendar, contacts, tasks through calendar, IIS (webserver) and data storage.

With 2007, they introduced several new features, including:

* Protection (anti-spam, antivirus etc.).
* Extensive Scripting language (Microsoft PowerShell).
* Increased allowed size of database and allowed amount of databases that can be run through Exchange.
* Outlook AnyWhere, a remote access to a web e-mail client.

== Problems I Ran Into and How to Fix ==

I started out on a different network than I was going to end up on, so my DNS had already put in all of the information required for that IP and network. This made everything a bit tricky since my client wouldn't be able to resolve anything as the DNS server is out of reach.

To fix it, I had to reinstall the role DNS server and let it reconfigure itself. Afterwards, everything worked without a hitch.

Trillex small business server 2008

2009-09-25T07:16:59Z

Trillex: /* Introduction */

= Deployment of Small Business Server 2008 =

== Introduction ==

For this week, I am going to deploy a Small Business Server 2008, that would be suitable for a "standard" business.

Just to give me some kind of aim, I will put up these demands for myself:

The company has 15 computers. They require logins which go through an exchange server. As any normal company, they also require emails, a website, personal login and a means of getting their files stored remotely on the server. A VPN connection for the workers as well as a means to manage the server remotely could also be mandatory.

=== Introduction to 64 bit Architecture ===

With Windows Server 2008, Microsoft made their operating system 64 bit. This is done for several reasons, but the "main" reason is that it supports more than 4 GB of memory. They've actually made it mandatory, so you cannot install it without less.

There are more to it, but mostly in memory allocations i.e. larger address spaces, wider registers and data paths. If a 64 bit operating system is handling a 64 bit compiled program or game, it will feel faster in that it got less limitations. This means that the processor can process more data at a time.

== Small Business Server 2008 ==

Microsoft have developed this branch of server operating systems to benefit smaller business that does not require big servers. By doing this, they've made a cheaper license that most business can afford with the ability to update.

=== Features and Components ===

*E-mail Server Application (Through Exchange).
*IIS Server Application. This is essentially a webserver.
*DHCP server
*DNS server
*Active Directory for handling Users and Groups
*Remote Web Workplace, Remote Desktop and VPN support
*Firewall
*Virus Scanner in the form of OneCare.

=== Limitations and Requirements ===

Windows Small Business Server 2008 got certain restrictions. This is because Microsoft wanted this to fit, as the name says, a small business so they put in some limitations to make the server operating system cheaper. Most business will not affected by these limitations. A lot of the limitations, like specific amount of space for emails, can be managed by implanting business policies - such as making sure you keep a tidy email account.

These limitations are:

*Only one SBS server in a domain. The domain can only handle more servers if these are of a different operating system, i.e. like linux, Windows Server etc.
*SBS is very picky about domains. It can only handle one and no child domains.
*Must be the root of the Active Directory forest.
*It is limited to 75 users (licenses).
*Earlier versions of SBS were limited to max 4 GB of memory. SBS 2008 requires a minimum of 4 GB and got a maximum limited of 32 GB. This is due to earlier versions being based on the x86 (32 bit) architecture while 2008 is based on x86-64 (64 bit). This change is because of Exchange Server 2007 is running in 64 bit.
*There are two different versions of SBS 2008. Standard Edition and Premium Edition. The difference between the two are: Premium includes a license to another Windows Server as well as MSSQL database.
*I am not certain if this limitation is still active in 2008 - but in Small Business Server 2003 service pack 2, the Exchange server limits you to 75 GB of emails.

If the business suddenly hits one of these limitations and needs to grow even further, it is possible to upgrade to a bigger license.

=== Installation of Small Server Business 2008 ===

Everybody knows how to press next and fill it out. So I will only fill this out with information that deems necessary to this project.

==== Partitioning ====

Normally, a server will have several harddrives in it and will run a certain kind of raid. Some people like to partition their harddrives to make it more "manageable" because they can assign certain drive letters to specific things, like documents for users etc. This is not at all necessary but can be easier to mange for certain people. I have decided not to do it - simply because it is not needed. By doing it this way, you will also force yourself to "read" drive/folder layouts and optimize them properly. This might be a linux thing but I prefer it this way.

In short, it's a matter of preference.

==== Updating and Virus Protection ====

Throughout the installation, it asks us whether or not we want to keep it up to date with updates and install it's virus scanner. We might as well, eh? Don't do it if you plan on using another one.

==== Post-installation ====

For the love of everything, remove UAC at once. It will make you hate everyone. Do that now.

=== Setting it Up ===

==== Internet Connectivity ====

An important part of a good business network, is having a constant connection to the Internet.

As we do not have a server with two ethernet interfaces, we are forced to do it a different way.

I believe that the best way to do it, is to let the router do the "sharing" and make the server give the IP, gateway and DNS information through it's DHCP server with a standard scope.

As I cannot do this with the current setup, I will not attempt it.

==== Adding Computers to the Domain ====

A pretty nice change in SBS is the ability to add computers. Not only does it add a computer, but it also installs certain tools to make sure that you can monitor a computer without having to physically look at it, i.e. it monitors virus scanner, status, updates etc and gives you a means to log on to it if needed. The way to do this is:

#Have a ready made XP installation. Login as Administrator.
#Go into a webbrowser and go to http://connect - or plug in a USB drive and tell the server to put the necessary files on there
#Follow the simple wizard.

==== Easy Configuration ====

Small Server Business 2008 has taken a hint from the unix world, have truly made it a lot easier to manage users and setting up the system. Upon installation, it starts up and installs the most commonly used services and utilities, such as DNS, IIS, Active Directory and more (These are also called roles and features). But the Windows SBS Console also allows for some amazing wizard options. If you want to add a user, it will automatically create a personal share for it, set the permissions for that folder as well as a "global" shared folder, create an email and send them a default "Welcome" email. Along with this, it can also print out this information. It is sort of a default way to do it, which can be very limiting to some.

While certainly streamlining the general process of managing and monitoring the server and the network, it can get very limiting in certain aspects and if you want to do something that isn't in the SBS Console, you will have to dig it out. If you are not familiar with earlier versions of SBS or Windows Server in general, you could get into a lot of problems doing something that was meant to be easy - like changing DHCP scope options, advanced permissions and logon scripts.

===== Shares =====

As stated above, the installation puts up a very standard, yet functional means of managing and taking care of shares. This is all very good but can be tedious to have to redo, since it just puts it in a standard folder called C:\Users\. If you have several partitions or harddrives, you'd most likely want to make use of them for user shares and documents. Thankfully, it is relatively easy to delete and redo the shares on different folders and is conveniently described in the SBS Console.

It is also with relative ease that you can make sure that it is only certain users who can enter certain directories/shares. It is done in the same way as most 2000+ Windows operating system - but I will just scratch it down quickly; You can do it the time consuming way or you can just add groups that certain people get into. This is all done through the standard Active Directory or can be done through the SBS Console.

I'd personally recommend keeping the sharing structure this way. There aren't many situations where you'd need to create it in a different way. So don't fix what isn't broken.

===== Users =====

As I noted earlier, there are several means of grouping up people, so mundane tasks are quickly done - like sending an email to a group of people can easily be done by putting them into a so called "Distribution Group". This creates the group on the email server and when mails are sent to this group, every one who is a member, will receive an email. Good for announcements.

You can also group people in security means which, surprisingly, is called "Security Groups". Using these security groups can be wise if you only want a specific amount of people being able to use, say, a printer or a cetain share. You can, for example, have a group just for the big bosses where they have access to just about everything.

Both of these groups can be attached to users during addition of users and groups.

=== Tools of Small Server Business 2008 ===

Microsoft have expanded a bit on their tools from 2003, most notably Windows SBS Console and Server Manager.

There are 2 different version of Windows SBS Console, normal and advanced mode - though all that advanced does, is add a few extra features under "Tasks".

These two tools cannot really be compared as they are governing two different aspects of the server. While Windows SBS Console is more monitoring, adding of users, shares etc - which is more like every day stuff - the Server Manager is exactly what is said in the name. It manages the server and keeps logs of everything running in the background. Essentially, it is a glorified Event Log as well as a Add/Remove Windows Components - just a lot more advanced in it's features.

Through Server Manager, you can add, remove, start, stop, restart and configure most "roles". Microsoft now call the background things going, i.e. like DNS, DHCP servers "roles". Which makes sense. The things on the frontend of it all, is then called features. These features include tools of varying kind - i.e. for deeper management of every specific role. For example, there are the role called DNS Server and for it, there is a feature called DNS Server Tools. It also has the ability to add "role services" which is essentially a module that can be added to a specific role. An example is that File Services can have a role service called Windows Search Service.

As stated earlier, it is also a event viewer. It keeps track of just about everything that is going on and lists if there has been an error on a specific role or if something has gone horribly wrong - much like what the SBS Console does, except this is deeper - it will show a warning symbol or something else in the main panel and then you can start digging into it.

Obviously, you can find and configure more in details if you go directly to the role/service itself than if you went through SBS Console or Server Manager. Both of them, however, conveniently links to this. A thing to note, is that whatever you add through SBS Console will be added to Active Directory, i.e. users and groups added will be added in it. If you view through Active Directory, you will see these in it's own directory, so you can sort through what changes came from SBS Console.

I am really loving these extra tools, that just makes server monitoring, and to some extend, managing a server a lot easier. Just having a monitor attached to it with SBS Console running constantly will make sure that a lot of errors are caught early on.

=== Remote Web Workplace ===

Again, a great feature from Small Server Business - The Remote Web Workplace is just what it says - a means to connect to work from home and have access to just about everything you need. Intranet website, e-mail and Remote Desktop Connection to any computer you are allowed to. Great for those who wants to clock in some extra hours from home. You can even expand it with Office AnyWhere which provides an online means of viewing, writing and using documents online.

To me, this makes VPN kind of obsolete unless you have a database tool or something that requires you to be connected to a VPN - but that could just as possible be done through Remote Desktop Connection. They still allow for VPN connection but it isn't as simple as with SBS 2003, that even allowed an easy application to be downloaded and used, streamlining the process for workers.

=== Windows Firewall ===

Firewall is, like all the other tools, preinstalled and setup. Firewall in SBS is very tightly integrated with the rest of the systems, which makes sure that the tools that need to go out, gets out and the things that need to go in, goes in.

Obviously, it got a deeper configuration, which can be accessed through the Server Manager tool.
Personally, I feel that this is the way a Firewall should be. When everything that is necessary to make a server/network run is already plotted in, you can just make minor changes and tweaks here and there for whatever you need to make use of.

=== SharePoint ===

SharePoint is a flexible "tool" from Microsoft. Essentially, it is a means to make webpages with ease using a preset form but it is more than that. It can be used as a sort of a file server or a "whiteboard" for work projects, groups and more where the workers can share their work, information etc. It is also a platform for various programs.

As an administrator, you must think it could be hell administering all of the SharePoint items that your business will make use of, but with most things Microsoft, you have a means to give other users group "leadership", so they can add/remove items themselves and generally configure their own item without having to contact their local administrator.

Through SharePoint, users or administrators can create "items" which can contain certain information or a workplan - making it an ideal platform to gather on and keep everybody up to date and synced.

A bit of a downside to SharePoint is that every site you make will, by default, make use of a new port. This means extra adminstration because you have to open up another port, depending if you are using a router or not, for every site you make.

== Network Diagram ==

This network diagram is suited for a very standard small business.

Note that since I do not have access to a computer with two ethernet interfaces, I have made it so I will not require this on the diagram. This can be a problem for certain businesses, since you cannot set up a proper firewall or monitor internet activity etc., except through a router's very limited monitoring tools and firewall. It is, however, possible.

[[Image:Sbs2008.png]]

It can be done in many ways, but this is a pretty good one for what we got.

Remember that this is not how it will look physically.

What we got is a router that connects to the internet. We could have connected the server directly to the router and the switch with it, but that could create a necessary burden on the router - which could strain the network if huge amounts of datas are passed through. You CAN do it but there is no reason to it, if you already got a switch handy. Why would it do this? Well, every packet going to the server would have to go into the inbuilt switch in the router as well as every packet aiming for the web, would have to go through it. Again, you can do it but it is not ideal.

Now that we cleared that up, we got a switch connected to the router. This switch is connected to the server and as many computers there are in the company. Notice that there easily could be more switches in the physical setup, due to computers being spread out in different departments and offices.

=== IP Table ===

{| border="1" class="wikitable"
|-
! IP
! Device
! DHCP or Static
! Gateway
! DNS
|-
| 192.168.1.1/24
| Router
| Static
|
|
|-
| 192.168.1.2/24
| SBS 2008 Server
| Static
|
|
|-
| 192.168.1.10-254/24
| Computers and Devices*
| DHCP
|
|
|}

<nowiki>
* Devices are network printers, IP phones and everything else that would require an IP.
</nowiki>

Pretty straightforward and easy.

=== How to Simulate at Mercantec ===

I do not have access to 15 computers or devices nor do I want to have to set up an entire Cisco Router just for this project, so I cut some corners on certain things but will still accomplish the same thing. I am only writing this here, so I can keep it organized and noted down.

<strike>After consulting Henrik about the network here, he suggested that I just use some IPs freely available here and create it out from that. These two are:</strike>

*<strike>192.168.138.128</strike>
*<strike>192.168.138.131</strike>

<strike>What I will do is give the server the first IP and the computer the second one. Because of this, I cannot install DHCP. I find that installing DHCP is pretty forward anyway and shouldn't need to be documented as we can just assume it is there. It is used for Internet Connectivity section and I will describe it like it is used like that. But if it is needed, let me know and I can find another way to do it.</strike>

After having tried the above, I've decided to just make a small network with just 2 computers in it with no connectivity to the internet. I enabled the scope, I described earlier and set it's gateway and DNS to the fictional router. I've updated both client and server so I shouldn't require any web access.

== Exchange Server 2007 ==

Small Server Business is using Exchange Server 2007.

Exchange Server got a lot of roles and functions that is tightly integrated into the very core of the operating system, providing one of it's main infrastructures together with Active Diectory.

Exchange major functions are that of e-mails, calendar, contacts, tasks through calendar, IIS (webserver) and data storage.

With 2007, they introduced several new features, including:

* Protection (anti-spam, antivirus etc.).
* Extensive Scripting language (Microsoft PowerShell).
* Increased allowed size of database and allowed amount of databases that can be run through Exchange.
* Outlook AnyWhere, a remote access to a web e-mail client.

== Problems I Ran Into and How to Fix ==

I started out on a different network than I was going to end up on, so my DNS had already put in all of the information required for that IP and network. This made everything a bit tricky since my client wouldn't be able to resolve anything as the DNS server is out of reach.

To fix it, I had to reinstall the role DNS server and let it reconfigure itself. Afterwards, everything worked without a hitch.

Trillex small business server 2008

2009-09-25T07:04:59Z

Trillex:

= Deployment of Small Business Server 2008 =

== Introduction ==

For this week, I am going to deploy a Small Business Server 2008, that would be suitable for a "standard" business.

Just to give me some kind of aim, I will put up these demands for myself:

The company got 15 computers. They require logins that goes through an exchange server. As any normal company, they also require emails, a website, personal login and a means of getting their files stored remotely on the server. A VPN connection for the workers as well as a means to manage the server remotely could also be mandatory.

=== Introduction to 64 bit Architecture ===

With Windows Server 2008, Microsoft made their operating system 64 bit. This is done for several reasons, but the "main" part of it is that it supports more than 4 GB of memory. They've actually made it mandatory, so you cannot install it without less.

There are more to it, but mostly in memory allocations i.e. larger address spaces, wider registers and data paths. If a 64 bit operating system is handling a 64 bit compiled program or game, it will feel faster in that it got less limitations. This means that the processor can process more data at a time.

== Small Business Server 2008 ==

Microsoft have developed this branch of server operating systems to benefit smaller business that does not require big servers. By doing this, they've made a cheaper license that most business can afford with the ability to update.

=== Features and Components ===

*E-mail Server Application (Through Exchange).
*IIS Server Application. This is essentially a webserver.
*DHCP server
*DNS server
*Active Directory for handling Users and Groups
*Remote Web Workplace, Remote Desktop and VPN support
*Firewall
*Virus Scanner in the form of OneCare.

=== Limitations and Requirements ===

Windows Small Business Server 2008 got certain restrictions. This is because Microsoft wanted this to fit, as the name says, a small business so they put in some limitations to make the server operating system cheaper. Most business will not affected by these limitations. A lot of the limitations, like specific amount of space for emails, can be managed by implanting business policies - such as making sure you keep a tidy email account.

These limitations are:

*Only one SBS server in a domain. The domain can only handle more servers if these are of a different operating system, i.e. like linux, Windows Server etc.
*SBS is very picky about domains. It can only handle one and no child domains.
*Must be the root of the Active Directory forest.
*It is limited to 75 users (licenses).
*Earlier versions of SBS were limited to max 4 GB of memory. SBS 2008 requires a minimum of 4 GB and got a maximum limited of 32 GB. This is due to earlier versions being based on the x86 (32 bit) architecture while 2008 is based on x86-64 (64 bit). This change is because of Exchange Server 2007 is running in 64 bit.
*There are two different versions of SBS 2008. Standard Edition and Premium Edition. The difference between the two are: Premium includes a license to another Windows Server as well as MSSQL database.
*I am not certain if this limitation is still active in 2008 - but in Small Business Server 2003 service pack 2, the Exchange server limits you to 75 GB of emails.

If the business suddenly hits one of these limitations and needs to grow even further, it is possible to upgrade to a bigger license.

=== Installation of Small Server Business 2008 ===

Everybody knows how to press next and fill it out. So I will only fill this out with information that deems necessary to this project.

==== Partitioning ====

Normally, a server will have several harddrives in it and will run a certain kind of raid. Some people like to partition their harddrives to make it more "manageable" because they can assign certain drive letters to specific things, like documents for users etc. This is not at all necessary but can be easier to mange for certain people. I have decided not to do it - simply because it is not needed. By doing it this way, you will also force yourself to "read" drive/folder layouts and optimize them properly. This might be a linux thing but I prefer it this way.

In short, it's a matter of preference.

==== Updating and Virus Protection ====

Throughout the installation, it asks us whether or not we want to keep it up to date with updates and install it's virus scanner. We might as well, eh? Don't do it if you plan on using another one.

==== Post-installation ====

For the love of everything, remove UAC at once. It will make you hate everyone. Do that now.

=== Setting it Up ===

==== Internet Connectivity ====

An important part of a good business network, is having a constant connection to the Internet.

As we do not have a server with two ethernet interfaces, we are forced to do it a different way.

I believe that the best way to do it, is to let the router do the "sharing" and make the server give the IP, gateway and DNS information through it's DHCP server with a standard scope.

As I cannot do this with the current setup, I will not attempt it.

==== Adding Computers to the Domain ====

A pretty nice change in SBS is the ability to add computers. Not only does it add a computer, but it also installs certain tools to make sure that you can monitor a computer without having to physically look at it, i.e. it monitors virus scanner, status, updates etc and gives you a means to log on to it if needed. The way to do this is:

#Have a ready made XP installation. Login as Administrator.
#Go into a webbrowser and go to http://connect - or plug in a USB drive and tell the server to put the necessary files on there
#Follow the simple wizard.

==== Easy Configuration ====

Small Server Business 2008 has taken a hint from the unix world, have truly made it a lot easier to manage users and setting up the system. Upon installation, it starts up and installs the most commonly used services and utilities, such as DNS, IIS, Active Directory and more (These are also called roles and features). But the Windows SBS Console also allows for some amazing wizard options. If you want to add a user, it will automatically create a personal share for it, set the permissions for that folder as well as a "global" shared folder, create an email and send them a default "Welcome" email. Along with this, it can also print out this information. It is sort of a default way to do it, which can be very limiting to some.

While certainly streamlining the general process of managing and monitoring the server and the network, it can get very limiting in certain aspects and if you want to do something that isn't in the SBS Console, you will have to dig it out. If you are not familiar with earlier versions of SBS or Windows Server in general, you could get into a lot of problems doing something that was meant to be easy - like changing DHCP scope options, advanced permissions and logon scripts.

===== Shares =====

As stated above, the installation puts up a very standard, yet functional means of managing and taking care of shares. This is all very good but can be tedious to have to redo, since it just puts it in a standard folder called C:\Users\. If you have several partitions or harddrives, you'd most likely want to make use of them for user shares and documents. Thankfully, it is relatively easy to delete and redo the shares on different folders and is conveniently described in the SBS Console.

It is also with relative ease that you can make sure that it is only certain users who can enter certain directories/shares. It is done in the same way as most 2000+ Windows operating system - but I will just scratch it down quickly; You can do it the time consuming way or you can just add groups that certain people get into. This is all done through the standard Active Directory or can be done through the SBS Console.

I'd personally recommend keeping the sharing structure this way. There aren't many situations where you'd need to create it in a different way. So don't fix what isn't broken.

===== Users =====

As I noted earlier, there are several means of grouping up people, so mundane tasks are quickly done - like sending an email to a group of people can easily be done by putting them into a so called "Distribution Group". This creates the group on the email server and when mails are sent to this group, every one who is a member, will receive an email. Good for announcements.

You can also group people in security means which, surprisingly, is called "Security Groups". Using these security groups can be wise if you only want a specific amount of people being able to use, say, a printer or a cetain share. You can, for example, have a group just for the big bosses where they have access to just about everything.

Both of these groups can be attached to users during addition of users and groups.

=== Tools of Small Server Business 2008 ===

Microsoft have expanded a bit on their tools from 2003, most notably Windows SBS Console and Server Manager.

There are 2 different version of Windows SBS Console, normal and advanced mode - though all that advanced does, is add a few extra features under "Tasks".

These two tools cannot really be compared as they are governing two different aspects of the server. While Windows SBS Console is more monitoring, adding of users, shares etc - which is more like every day stuff - the Server Manager is exactly what is said in the name. It manages the server and keeps logs of everything running in the background. Essentially, it is a glorified Event Log as well as a Add/Remove Windows Components - just a lot more advanced in it's features.

Through Server Manager, you can add, remove, start, stop, restart and configure most "roles". Microsoft now call the background things going, i.e. like DNS, DHCP servers "roles". Which makes sense. The things on the frontend of it all, is then called features. These features include tools of varying kind - i.e. for deeper management of every specific role. For example, there are the role called DNS Server and for it, there is a feature called DNS Server Tools. It also has the ability to add "role services" which is essentially a module that can be added to a specific role. An example is that File Services can have a role service called Windows Search Service.

As stated earlier, it is also a event viewer. It keeps track of just about everything that is going on and lists if there has been an error on a specific role or if something has gone horribly wrong - much like what the SBS Console does, except this is deeper - it will show a warning symbol or something else in the main panel and then you can start digging into it.

Obviously, you can find and configure more in details if you go directly to the role/service itself than if you went through SBS Console or Server Manager. Both of them, however, conveniently links to this. A thing to note, is that whatever you add through SBS Console will be added to Active Directory, i.e. users and groups added will be added in it. If you view through Active Directory, you will see these in it's own directory, so you can sort through what changes came from SBS Console.

I am really loving these extra tools, that just makes server monitoring, and to some extend, managing a server a lot easier. Just having a monitor attached to it with SBS Console running constantly will make sure that a lot of errors are caught early on.

=== Remote Web Workplace ===

Again, a great feature from Small Server Business - The Remote Web Workplace is just what it says - a means to connect to work from home and have access to just about everything you need. Intranet website, e-mail and Remote Desktop Connection to any computer you are allowed to. Great for those who wants to clock in some extra hours from home. You can even expand it with Office AnyWhere which provides an online means of viewing, writing and using documents online.

To me, this makes VPN kind of obsolete unless you have a database tool or something that requires you to be connected to a VPN - but that could just as possible be done through Remote Desktop Connection. They still allow for VPN connection but it isn't as simple as with SBS 2003, that even allowed an easy application to be downloaded and used, streamlining the process for workers.

=== Windows Firewall ===

Firewall is, like all the other tools, preinstalled and setup. Firewall in SBS is very tightly integrated with the rest of the systems, which makes sure that the tools that need to go out, gets out and the things that need to go in, goes in.

Obviously, it got a deeper configuration, which can be accessed through the Server Manager tool.
Personally, I feel that this is the way a Firewall should be. When everything that is necessary to make a server/network run is already plotted in, you can just make minor changes and tweaks here and there for whatever you need to make use of.

=== SharePoint ===

SharePoint is a flexible "tool" from Microsoft. Essentially, it is a means to make webpages with ease using a preset form but it is more than that. It can be used as a sort of a file server or a "whiteboard" for work projects, groups and more where the workers can share their work, information etc. It is also a platform for various programs.

As an administrator, you must think it could be hell administering all of the SharePoint items that your business will make use of, but with most things Microsoft, you have a means to give other users group "leadership", so they can add/remove items themselves and generally configure their own item without having to contact their local administrator.

Through SharePoint, users or administrators can create "items" which can contain certain information or a workplan - making it an ideal platform to gather on and keep everybody up to date and synced.

A bit of a downside to SharePoint is that every site you make will, by default, make use of a new port. This means extra adminstration because you have to open up another port, depending if you are using a router or not, for every site you make.

== Network Diagram ==

This network diagram is suited for a very standard small business.

Note that since I do not have access to a computer with two ethernet interfaces, I have made it so I will not require this on the diagram. This can be a problem for certain businesses, since you cannot set up a proper firewall or monitor internet activity etc., except through a router's very limited monitoring tools and firewall. It is, however, possible.

[[Image:Sbs2008.png]]

It can be done in many ways, but this is a pretty good one for what we got.

Remember that this is not how it will look physically.

What we got is a router that connects to the internet. We could have connected the server directly to the router and the switch with it, but that could create a necessary burden on the router - which could strain the network if huge amounts of datas are passed through. You CAN do it but there is no reason to it, if you already got a switch handy. Why would it do this? Well, every packet going to the server would have to go into the inbuilt switch in the router as well as every packet aiming for the web, would have to go through it. Again, you can do it but it is not ideal.

Now that we cleared that up, we got a switch connected to the router. This switch is connected to the server and as many computers there are in the company. Notice that there easily could be more switches in the physical setup, due to computers being spread out in different departments and offices.

=== IP Table ===

{| border="1" class="wikitable"
|-
! IP
! Device
! DHCP or Static
! Gateway
! DNS
|-
| 192.168.1.1/24
| Router
| Static
|
|
|-
| 192.168.1.2/24
| SBS 2008 Server
| Static
|
|
|-
| 192.168.1.10-254/24
| Computers and Devices*
| DHCP
|
|
|}

<nowiki>
* Devices are network printers, IP phones and everything else that would require an IP.
</nowiki>

Pretty straightforward and easy.

=== How to Simulate at Mercantec ===

I do not have access to 15 computers or devices nor do I want to have to set up an entire Cisco Router just for this project, so I cut some corners on certain things but will still accomplish the same thing. I am only writing this here, so I can keep it organized and noted down.

<strike>After consulting Henrik about the network here, he suggested that I just use some IPs freely available here and create it out from that. These two are:</strike>

*<strike>192.168.138.128</strike>
*<strike>192.168.138.131</strike>

<strike>What I will do is give the server the first IP and the computer the second one. Because of this, I cannot install DHCP. I find that installing DHCP is pretty forward anyway and shouldn't need to be documented as we can just assume it is there. It is used for Internet Connectivity section and I will describe it like it is used like that. But if it is needed, let me know and I can find another way to do it.</strike>

After having tried the above, I've decided to just make a small network with just 2 computers in it with no connectivity to the internet. I enabled the scope, I described earlier and set it's gateway and DNS to the fictional router. I've updated both client and server so I shouldn't require any web access.

== Exchange Server 2007 ==

Small Server Business is using Exchange Server 2007.

Exchange Server got a lot of roles and functions that is tightly integrated into the very core of the operating system, providing one of it's main infrastructures together with Active Diectory.

Exchange major functions are that of e-mails, calendar, contacts, tasks through calendar, IIS (webserver) and data storage.

With 2007, they introduced several new features, including:

* Protection (anti-spam, antivirus etc.).
* Extensive Scripting language (Microsoft PowerShell).
* Increased allowed size of database and allowed amount of databases that can be run through Exchange.
* Outlook AnyWhere, a remote access to a web e-mail client.

== Problems I Ran Into and How to Fix ==

I started out on a different network than I was going to end up on, so my DNS had already put in all of the information required for that IP and network. This made everything a bit tricky since my client wouldn't be able to resolve anything as the DNS server is out of reach.

To fix it, I had to reinstall the role DNS server and let it reconfigure itself. Afterwards, everything worked without a hitch.

Trillex small business server 2008

2009-09-25T07:02:58Z

Trillex: /* Shares */

Day 4 Tasks: SBS 2008:
--------------------------------
Windows Share Points Services 3?
Share Points Items?
Share Points Roles?
Customizing a Share point Site ?
Windows Exchange Server 2007 theory ?
Distribution group vs Security group ?

= Deployment of Small Business Server 2008 =

THIS IS AN UNDERGOING PROJECT. MOST THINGS, IF NOT ALL, WILL CHANGE DURING THIS WEEK!

IF YOU SEE AN ERROR, CONTACT ME.

== Introduction ==

For this week, I am going to deploy a Small Business Server 2008, that would be suitable for a "standard" business.

Just to give me some kind of aim, I will put up these demands for myself:

The company got 15 computers. They require logins that goes through an exchange server. As any normal company, they also require emails, a website, personal login and a means of getting their files stored remotely on the server. A VPN connection for the workers as well as a means to manage the server remotely could also be mandatory.

=== Introduction to 64 bit Architecture ===

With Windows Server 2008, Microsoft made their operating system 64 bit. This is done for several reasons, but the "main" part of it is that it supports more than 4 GB of memory. They've actually made it mandatory, so you cannot install it without less.

There are more to it, but mostly in memory allocations i.e. larger address spaces, wider registers and data paths. If a 64 bit operating system is handling a 64 bit compiled program or game, it will feel faster in that it got less limitations. This means that the processor can process more data at a time.

== Small Business Server 2008 ==

Microsoft have developed this branch of server operating systems to benefit smaller business that does not require big servers. By doing this, they've made a cheaper license that most business can afford with the ability to update.

=== Features and Components ===

*E-mail Server Application (Through Exchange).
*IIS Server Application. This is essentially a webserver.
*DHCP server
*DNS server
*Active Directory for handling Users and Groups
*Remote Web Workplace, Remote Desktop and VPN support
*Firewall
*Virus Scanner in the form of OneCare.

=== Limitations and Requirements ===

Windows Small Business Server 2008 got certain restrictions. This is because Microsoft wanted this to fit, as the name says, a small business so they put in some limitations to make the server operating system cheaper. Most business will not affected by these limitations. A lot of the limitations, like specific amount of space for emails, can be managed by implanting business policies - such as making sure you keep a tidy email account.

These limitations are:

*Only one SBS server in a domain. The domain can only handle more servers if these are of a different operating system, i.e. like linux, Windows Server etc.
*SBS is very picky about domains. It can only handle one and no child domains.
*Must be the root of the Active Directory forest.
*It is limited to 75 users (licenses).
*Earlier versions of SBS were limited to max 4 GB of memory. SBS 2008 requires a minimum of 4 GB and got a maximum limited of 32 GB. This is due to earlier versions being based on the x86 (32 bit) architecture while 2008 is based on x86-64 (64 bit). This change is because of Exchange Server 2007 is running in 64 bit.
*There are two different versions of SBS 2008. Standard Edition and Premium Edition. The difference between the two are: Premium includes a license to another Windows Server as well as MSSQL database.
*I am not certain if this limitation is still active in 2008 - but in Small Business Server 2003 service pack 2, the Exchange server limits you to 75 GB of emails.

If the business suddenly hits one of these limitations and needs to grow even further, it is possible to upgrade to a bigger license.

=== Installation of Small Server Business 2008 ===

Everybody knows how to press next and fill it out. So I will only fill this out with information that deems necessary to this project.

==== Partitioning ====

Normally, a server will have several harddrives in it and will run a certain kind of raid. Some people like to partition their harddrives to make it more "manageable" because they can assign certain drive letters to specific things, like documents for users etc. This is not at all necessary but can be easier to mange for certain people. I have decided not to do it - simply because it is not needed. By doing it this way, you will also force yourself to "read" drive/folder layouts and optimize them properly. This might be a linux thing but I prefer it this way.

In short, it's a matter of preference.

==== Updating and Virus Protection ====

Throughout the installation, it asks us whether or not we want to keep it up to date with updates and install it's virus scanner. We might as well, eh? Don't do it if you plan on using another one.

==== Post-installation ====

For the love of everything, remove UAC at once. It will make you hate everyone. Do that now.

=== Setting it Up ===

==== Internet Connectivity ====

An important part of a good business network, is having a constant connection to the Internet.

As we do not have a server with two ethernet interfaces, we are forced to do it a different way.

I believe that the best way to do it, is to let the router do the "sharing" and make the server give the IP, gateway and DNS information through it's DHCP server with a standard scope.

As I cannot do this with the current setup, I will not attempt it.

==== Adding Computers to the Domain ====

A pretty nice change in SBS is the ability to add computers. Not only does it add a computer, but it also installs certain tools to make sure that you can monitor a computer without having to physically look at it, i.e. it monitors virus scanner, status, updates etc and gives you a means to log on to it if needed. The way to do this is:

#Have a ready made XP installation. Login as Administrator.
#Go into a webbrowser and go to http://connect - or plug in a USB drive and tell the server to put the necessary files on there
#Follow the simple wizard.

==== Easy Configuration ====

Small Server Business 2008 has taken a hint from the unix world, have truly made it a lot easier to manage users and setting up the system. Upon installation, it starts up and installs the most commonly used services and utilities, such as DNS, IIS, Active Directory and more (These are also called roles and features). But the Windows SBS Console also allows for some amazing wizard options. If you want to add a user, it will automatically create a personal share for it, set the permissions for that folder as well as a "global" shared folder, create an email and send them a default "Welcome" email. Along with this, it can also print out this information. It is sort of a default way to do it, which can be very limiting to some.

While certainly streamlining the general process of managing and monitoring the server and the network, it can get very limiting in certain aspects and if you want to do something that isn't in the SBS Console, you will have to dig it out. If you are not familiar with earlier versions of SBS or Windows Server in general, you could get into a lot of problems doing something that was meant to be easy - like changing DHCP scope options, advanced permissions and logon scripts.

===== Shares =====

As stated above, the installation puts up a very standard, yet functional means of managing and taking care of shares. This is all very good but can be tedious to have to redo, since it just puts it in a standard folder called C:\Users\. If you have several partitions or harddrives, you'd most likely want to make use of them for user shares and documents. Thankfully, it is relatively easy to delete and redo the shares on different folders and is conveniently described in the SBS Console.

It is also with relative ease that you can make sure that it is only certain users who can enter certain directories/shares. It is done in the same way as most 2000+ Windows operating system - but I will just scratch it down quickly; You can do it the time consuming way or you can just add groups that certain people get into. This is all done through the standard Active Directory or can be done through the SBS Console.

I'd personally recommend keeping the sharing structure this way. There aren't many situations where you'd need to create it in a different way. So don't fix what isn't broken.

===== Users =====

As I noted earlier, there are several means of grouping up people, so mundane tasks are quickly done - like sending an email to a group of people can easily be done by putting them into a so called "Distribution Group". This creates the group on the email server and when mails are sent to this group, every one who is a member, will receive an email. Good for announcements.

You can also group people in security means which, surprisingly, is called "Security Groups". Using these security groups can be wise if you only want a specific amount of people being able to use, say, a printer or a cetain share. You can, for example, have a group just for the big bosses where they have access to just about everything.

Both of these groups can be attached to users during addition of users and groups.

=== Tools of Small Server Business 2008 ===

Microsoft have expanded a bit on their tools from 2003, most notably Windows SBS Console and Server Manager.

There are 2 different version of Windows SBS Console, normal and advanced mode - though all that advanced does, is add a few extra features under "Tasks".

These two tools cannot really be compared as they are governing two different aspects of the server. While Windows SBS Console is more monitoring, adding of users, shares etc - which is more like every day stuff - the Server Manager is exactly what is said in the name. It manages the server and keeps logs of everything running in the background. Essentially, it is a glorified Event Log as well as a Add/Remove Windows Components - just a lot more advanced in it's features.

Through Server Manager, you can add, remove, start, stop, restart and configure most "roles". Microsoft now call the background things going, i.e. like DNS, DHCP servers "roles". Which makes sense. The things on the frontend of it all, is then called features. These features include tools of varying kind - i.e. for deeper management of every specific role. For example, there are the role called DNS Server and for it, there is a feature called DNS Server Tools. It also has the ability to add "role services" which is essentially a module that can be added to a specific role. An example is that File Services can have a role service called Windows Search Service.

As stated earlier, it is also a event viewer. It keeps track of just about everything that is going on and lists if there has been an error on a specific role or if something has gone horribly wrong - much like what the SBS Console does, except this is deeper - it will show a warning symbol or something else in the main panel and then you can start digging into it.

Obviously, you can find and configure more in details if you go directly to the role/service itself than if you went through SBS Console or Server Manager. Both of them, however, conveniently links to this. A thing to note, is that whatever you add through SBS Console will be added to Active Directory, i.e. users and groups added will be added in it. If you view through Active Directory, you will see these in it's own directory, so you can sort through what changes came from SBS Console.

I am really loving these extra tools, that just makes server monitoring, and to some extend, managing a server a lot easier. Just having a monitor attached to it with SBS Console running constantly will make sure that a lot of errors are caught early on.

=== Remote Web Workplace ===

Again, a great feature from Small Server Business - The Remote Web Workplace is just what it says - a means to connect to work from home and have access to just about everything you need. Intranet website, e-mail and Remote Desktop Connection to any computer you are allowed to. Great for those who wants to clock in some extra hours from home. You can even expand it with Office AnyWhere which provides an online means of viewing, writing and using documents online.

To me, this makes VPN kind of obsolete unless you have a database tool or something that requires you to be connected to a VPN - but that could just as possible be done through Remote Desktop Connection. They still allow for VPN connection but it isn't as simple as with SBS 2003, that even allowed an easy application to be downloaded and used, streamlining the process for workers.

=== Windows Firewall ===

Firewall is, like all the other tools, preinstalled and setup. Firewall in SBS is very tightly integrated with the rest of the systems, which makes sure that the tools that need to go out, gets out and the things that need to go in, goes in.

Obviously, it got a deeper configuration, which can be accessed through the Server Manager tool.
Personally, I feel that this is the way a Firewall should be. When everything that is necessary to make a server/network run is already plotted in, you can just make minor changes and tweaks here and there for whatever you need to make use of.

=== SharePoint ===

SharePoint is a flexible "tool" from Microsoft. Essentially, it is a means to make webpages with ease using a preset form but it is more than that. It can be used as a sort of a file server or a "whiteboard" for work projects, groups and more where the workers can share their work, information etc. It is also a platform for various programs.

As an administrator, you must think it could be hell administering all of the SharePoint items that your business will make use of, but with most things Microsoft, you have a means to give other users group "leadership", so they can add/remove items themselves and generally configure their own item without having to contact their local administrator.

Through SharePoint, users or administrators can create "items" which can contain certain information or a workplan - making it an ideal platform to gather on and keep everybody up to date and synced.

A bit of a downside to SharePoint is that every site you make will, by default, make use of a new port. This means extra adminstration because you have to open up another port, depending if you are using a router or not, for every site you make.

== Network Diagram ==

This network diagram is suited for a very standard small business.

Note that since I do not have access to a computer with two ethernet interfaces, I have made it so I will not require this on the diagram. This can be a problem for certain businesses, since you cannot set up a proper firewall or monitor internet activity etc., except through a router's very limited monitoring tools and firewall. It is, however, possible.

[[Image:Sbs2008.png]]

It can be done in many ways, but this is a pretty good one for what we got.

Remember that this is not how it will look physically.

What we got is a router that connects to the internet. We could have connected the server directly to the router and the switch with it, but that could create a necessary burden on the router - which could strain the network if huge amounts of datas are passed through. You CAN do it but there is no reason to it, if you already got a switch handy. Why would it do this? Well, every packet going to the server would have to go into the inbuilt switch in the router as well as every packet aiming for the web, would have to go through it. Again, you can do it but it is not ideal.

Now that we cleared that up, we got a switch connected to the router. This switch is connected to the server and as many computers there are in the company. Notice that there easily could be more switches in the physical setup, due to computers being spread out in different departments and offices.

=== IP Table ===

{| border="1" class="wikitable"
|-
! IP
! Device
! DHCP or Static
! Gateway
! DNS
|-
| 192.168.1.1/24
| Router
| Static
|
|
|-
| 192.168.1.2/24
| SBS 2008 Server
| Static
|
|
|-
| 192.168.1.10-254/24
| Computers and Devices*
| DHCP
|
|
|}

<nowiki>
* Devices are network printers, IP phones and everything else that would require an IP.
</nowiki>

Pretty straightforward and easy.

=== How to Simulate at Mercantec ===

I do not have access to 15 computers or devices nor do I want to have to set up an entire Cisco Router just for this project, so I cut some corners on certain things but will still accomplish the same thing. I am only writing this here, so I can keep it organized and noted down.

<strike>After consulting Henrik about the network here, he suggested that I just use some IPs freely available here and create it out from that. These two are:</strike>

*<strike>192.168.138.128</strike>
*<strike>192.168.138.131</strike>

<strike>What I will do is give the server the first IP and the computer the second one. Because of this, I cannot install DHCP. I find that installing DHCP is pretty forward anyway and shouldn't need to be documented as we can just assume it is there. It is used for Internet Connectivity section and I will describe it like it is used like that. But if it is needed, let me know and I can find another way to do it.</strike>

After having tried the above, I've decided to just make a small network with just 2 computers in it with no connectivity to the internet. I enabled the scope, I described earlier and set it's gateway and DNS to the fictional router. I've updated both client and server so I shouldn't require any web access.

== Exchange Server 2007 ==

Small Server Business is using Exchange Server 2007.

Exchange Server got a lot of roles and functions that is tightly integrated into the very core of the operating system, providing one of it's main infrastructures together with Active Diectory.

Exchange major functions are that of e-mails, calendar, contacts, tasks through calendar, IIS (webserver) and data storage.

With 2007, they introduced several new features, including:

* Protection (anti-spam, antivirus etc.).
* Extensive Scripting language (Microsoft PowerShell).
* Increased allowed size of database and allowed amount of databases that can be run through Exchange.
* Outlook AnyWhere, a remote access to a web e-mail client.

== Problems I Ran Into and How to Fix ==

I started out on a different network than I was going to end up on, so my DNS had already put in all of the information required for that IP and network. This made everything a bit tricky since my client wouldn't be able to resolve anything as the DNS server is out of reach.

To fix it, I had to reinstall the role DNS server and let it reconfigure itself. Afterwards, everything worked without a hitch.

Trillex small business server 2008

2009-09-25T06:55:06Z

Trillex: /* Problems I Ran Into and How to Fix */

Day 4 Tasks: SBS 2008:
--------------------------------
Windows Share Points Services 3?
Share Points Items?
Share Points Roles?
Customizing a Share point Site ?
Windows Exchange Server 2007 theory ?
Distribution group vs Security group ?

= Deployment of Small Business Server 2008 =

THIS IS AN UNDERGOING PROJECT. MOST THINGS, IF NOT ALL, WILL CHANGE DURING THIS WEEK!

IF YOU SEE AN ERROR, CONTACT ME.

== Introduction ==

For this week, I am going to deploy a Small Business Server 2008, that would be suitable for a "standard" business.

Just to give me some kind of aim, I will put up these demands for myself:

The company got 15 computers. They require logins that goes through an exchange server. As any normal company, they also require emails, a website, personal login and a means of getting their files stored remotely on the server. A VPN connection for the workers as well as a means to manage the server remotely could also be mandatory.

=== Introduction to 64 bit Architecture ===

With Windows Server 2008, Microsoft made their operating system 64 bit. This is done for several reasons, but the "main" part of it is that it supports more than 4 GB of memory. They've actually made it mandatory, so you cannot install it without less.

There are more to it, but mostly in memory allocations i.e. larger address spaces, wider registers and data paths. If a 64 bit operating system is handling a 64 bit compiled program or game, it will feel faster in that it got less limitations. This means that the processor can process more data at a time.

== Small Business Server 2008 ==

Microsoft have developed this branch of server operating systems to benefit smaller business that does not require big servers. By doing this, they've made a cheaper license that most business can afford with the ability to update.

=== Features and Components ===

*E-mail Server Application (Through Exchange).
*IIS Server Application. This is essentially a webserver.
*DHCP server
*DNS server
*Active Directory for handling Users and Groups
*Remote Web Workplace, Remote Desktop and VPN support
*Firewall
*Virus Scanner in the form of OneCare.

=== Limitations and Requirements ===

Windows Small Business Server 2008 got certain restrictions. This is because Microsoft wanted this to fit, as the name says, a small business so they put in some limitations to make the server operating system cheaper. Most business will not affected by these limitations. A lot of the limitations, like specific amount of space for emails, can be managed by implanting business policies - such as making sure you keep a tidy email account.

These limitations are:

*Only one SBS server in a domain. The domain can only handle more servers if these are of a different operating system, i.e. like linux, Windows Server etc.
*SBS is very picky about domains. It can only handle one and no child domains.
*Must be the root of the Active Directory forest.
*It is limited to 75 users (licenses).
*Earlier versions of SBS were limited to max 4 GB of memory. SBS 2008 requires a minimum of 4 GB and got a maximum limited of 32 GB. This is due to earlier versions being based on the x86 (32 bit) architecture while 2008 is based on x86-64 (64 bit). This change is because of Exchange Server 2007 is running in 64 bit.
*There are two different versions of SBS 2008. Standard Edition and Premium Edition. The difference between the two are: Premium includes a license to another Windows Server as well as MSSQL database.
*I am not certain if this limitation is still active in 2008 - but in Small Business Server 2003 service pack 2, the Exchange server limits you to 75 GB of emails.

If the business suddenly hits one of these limitations and needs to grow even further, it is possible to upgrade to a bigger license.

=== Installation of Small Server Business 2008 ===

Everybody knows how to press next and fill it out. So I will only fill this out with information that deems necessary to this project.

==== Partitioning ====

Normally, a server will have several harddrives in it and will run a certain kind of raid. Some people like to partition their harddrives to make it more "manageable" because they can assign certain drive letters to specific things, like documents for users etc. This is not at all necessary but can be easier to mange for certain people. I have decided not to do it - simply because it is not needed. By doing it this way, you will also force yourself to "read" drive/folder layouts and optimize them properly. This might be a linux thing but I prefer it this way.

In short, it's a matter of preference.

==== Updating and Virus Protection ====

Throughout the installation, it asks us whether or not we want to keep it up to date with updates and install it's virus scanner. We might as well, eh? Don't do it if you plan on using another one.

==== Post-installation ====

For the love of everything, remove UAC at once. It will make you hate everyone. Do that now.

=== Setting it Up ===

==== Internet Connectivity ====

An important part of a good business network, is having a constant connection to the Internet.

As we do not have a server with two ethernet interfaces, we are forced to do it a different way.

I believe that the best way to do it, is to let the router do the "sharing" and make the server give the IP, gateway and DNS information through it's DHCP server with a standard scope.

As I cannot do this with the current setup, I will not attempt it.

==== Adding Computers to the Domain ====

A pretty nice change in SBS is the ability to add computers. Not only does it add a computer, but it also installs certain tools to make sure that you can monitor a computer without having to physically look at it, i.e. it monitors virus scanner, status, updates etc and gives you a means to log on to it if needed. The way to do this is:

#Have a ready made XP installation. Login as Administrator.
#Go into a webbrowser and go to http://connect - or plug in a USB drive and tell the server to put the necessary files on there
#Follow the simple wizard.

==== Easy Configuration ====

Small Server Business 2008 has taken a hint from the unix world, have truly made it a lot easier to manage users and setting up the system. Upon installation, it starts up and installs the most commonly used services and utilities, such as DNS, IIS, Active Directory and more (These are also called roles and features). But the Windows SBS Console also allows for some amazing wizard options. If you want to add a user, it will automatically create a personal share for it, set the permissions for that folder as well as a "global" shared folder, create an email and send them a default "Welcome" email. Along with this, it can also print out this information. It is sort of a default way to do it, which can be very limiting to some.

While certainly streamlining the general process of managing and monitoring the server and the network, it can get very limiting in certain aspects and if you want to do something that isn't in the SBS Console, you will have to dig it out. If you are not familiar with earlier versions of SBS or Windows Server in general, you could get into a lot of problems doing something that was meant to be easy - like changing DHCP scope options, advanced permissions and logon scripts.

===== Shares =====

As stated above, the installation puts up a very standard, yet functional means of managing and taking care of shares. This is all very good but can be tedious to have to redo, since it just puts it in a standard folder called C:\Users\. If you have several partitions or harddrives, you'd most likely want to make use of them for user shares and documents. Thankfully, it is relatively easy to delete and redo the shares on different folders and is conveniently described in the SBS Console.

It is also with relative ease that you can make sure that it is only certain users who can enter certain directories/shares. It is done in the same way as most 2000+ Windows operating system - but I will just scratch it down quickly; You can do it the time consuming way or you can just add groups that certain people get into. This is all done through the standard Active Directory or can be done through the SBS Console.

I'd personally recommend keeping the sharing structure this way. There aren't many situations where you'd need to create it in a different way. So don't fix what isn't broken.

=== Tools of Small Server Business 2008 ===

Microsoft have expanded a bit on their tools from 2003, most notably Windows SBS Console and Server Manager.

There are 2 different version of Windows SBS Console, normal and advanced mode - though all that advanced does, is add a few extra features under "Tasks".

These two tools cannot really be compared as they are governing two different aspects of the server. While Windows SBS Console is more monitoring, adding of users, shares etc - which is more like every day stuff - the Server Manager is exactly what is said in the name. It manages the server and keeps logs of everything running in the background. Essentially, it is a glorified Event Log as well as a Add/Remove Windows Components - just a lot more advanced in it's features.

Through Server Manager, you can add, remove, start, stop, restart and configure most "roles". Microsoft now call the background things going, i.e. like DNS, DHCP servers "roles". Which makes sense. The things on the frontend of it all, is then called features. These features include tools of varying kind - i.e. for deeper management of every specific role. For example, there are the role called DNS Server and for it, there is a feature called DNS Server Tools. It also has the ability to add "role services" which is essentially a module that can be added to a specific role. An example is that File Services can have a role service called Windows Search Service.

As stated earlier, it is also a event viewer. It keeps track of just about everything that is going on and lists if there has been an error on a specific role or if something has gone horribly wrong - much like what the SBS Console does, except this is deeper - it will show a warning symbol or something else in the main panel and then you can start digging into it.

Obviously, you can find and configure more in details if you go directly to the role/service itself than if you went through SBS Console or Server Manager. Both of them, however, conveniently links to this. A thing to note, is that whatever you add through SBS Console will be added to Active Directory, i.e. users and groups added will be added in it. If you view through Active Directory, you will see these in it's own directory, so you can sort through what changes came from SBS Console.

I am really loving these extra tools, that just makes server monitoring, and to some extend, managing a server a lot easier. Just having a monitor attached to it with SBS Console running constantly will make sure that a lot of errors are caught early on.

=== Remote Web Workplace ===

Again, a great feature from Small Server Business - The Remote Web Workplace is just what it says - a means to connect to work from home and have access to just about everything you need. Intranet website, e-mail and Remote Desktop Connection to any computer you are allowed to. Great for those who wants to clock in some extra hours from home. You can even expand it with Office AnyWhere which provides an online means of viewing, writing and using documents online.

To me, this makes VPN kind of obsolete unless you have a database tool or something that requires you to be connected to a VPN - but that could just as possible be done through Remote Desktop Connection. They still allow for VPN connection but it isn't as simple as with SBS 2003, that even allowed an easy application to be downloaded and used, streamlining the process for workers.

=== Windows Firewall ===

Firewall is, like all the other tools, preinstalled and setup. Firewall in SBS is very tightly integrated with the rest of the systems, which makes sure that the tools that need to go out, gets out and the things that need to go in, goes in.

Obviously, it got a deeper configuration, which can be accessed through the Server Manager tool.
Personally, I feel that this is the way a Firewall should be. When everything that is necessary to make a server/network run is already plotted in, you can just make minor changes and tweaks here and there for whatever you need to make use of.

=== SharePoint ===

SharePoint is a flexible "tool" from Microsoft. Essentially, it is a means to make webpages with ease using a preset form but it is more than that. It can be used as a sort of a file server or a "whiteboard" for work projects, groups and more where the workers can share their work, information etc. It is also a platform for various programs.

As an administrator, you must think it could be hell administering all of the SharePoint items that your business will make use of, but with most things Microsoft, you have a means to give other users group "leadership", so they can add/remove items themselves and generally configure their own item without having to contact their local administrator.

Through SharePoint, users or administrators can create "items" which can contain certain information or a workplan - making it an ideal platform to gather on and keep everybody up to date and synced.

A bit of a downside to SharePoint is that every site you make will, by default, make use of a new port. This means extra adminstration because you have to open up another port, depending if you are using a router or not, for every site you make.

== Network Diagram ==

This network diagram is suited for a very standard small business.

Note that since I do not have access to a computer with two ethernet interfaces, I have made it so I will not require this on the diagram. This can be a problem for certain businesses, since you cannot set up a proper firewall or monitor internet activity etc., except through a router's very limited monitoring tools and firewall. It is, however, possible.

[[Image:Sbs2008.png]]

It can be done in many ways, but this is a pretty good one for what we got.

Remember that this is not how it will look physically.

What we got is a router that connects to the internet. We could have connected the server directly to the router and the switch with it, but that could create a necessary burden on the router - which could strain the network if huge amounts of datas are passed through. You CAN do it but there is no reason to it, if you already got a switch handy. Why would it do this? Well, every packet going to the server would have to go into the inbuilt switch in the router as well as every packet aiming for the web, would have to go through it. Again, you can do it but it is not ideal.

Now that we cleared that up, we got a switch connected to the router. This switch is connected to the server and as many computers there are in the company. Notice that there easily could be more switches in the physical setup, due to computers being spread out in different departments and offices.

=== IP Table ===

{| border="1" class="wikitable"
|-
! IP
! Device
! DHCP or Static
! Gateway
! DNS
|-
| 192.168.1.1/24
| Router
| Static
|
|
|-
| 192.168.1.2/24
| SBS 2008 Server
| Static
|
|
|-
| 192.168.1.10-254/24
| Computers and Devices*
| DHCP
|
|
|}

<nowiki>
* Devices are network printers, IP phones and everything else that would require an IP.
</nowiki>

Pretty straightforward and easy.

=== How to Simulate at Mercantec ===

I do not have access to 15 computers or devices nor do I want to have to set up an entire Cisco Router just for this project, so I cut some corners on certain things but will still accomplish the same thing. I am only writing this here, so I can keep it organized and noted down.

<strike>After consulting Henrik about the network here, he suggested that I just use some IPs freely available here and create it out from that. These two are:</strike>

*<strike>192.168.138.128</strike>
*<strike>192.168.138.131</strike>

<strike>What I will do is give the server the first IP and the computer the second one. Because of this, I cannot install DHCP. I find that installing DHCP is pretty forward anyway and shouldn't need to be documented as we can just assume it is there. It is used for Internet Connectivity section and I will describe it like it is used like that. But if it is needed, let me know and I can find another way to do it.</strike>

After having tried the above, I've decided to just make a small network with just 2 computers in it with no connectivity to the internet. I enabled the scope, I described earlier and set it's gateway and DNS to the fictional router. I've updated both client and server so I shouldn't require any web access.

== Exchange Server 2007 ==

Small Server Business is using Exchange Server 2007.

Exchange Server got a lot of roles and functions that is tightly integrated into the very core of the operating system, providing one of it's main infrastructures together with Active Diectory.

Exchange major functions are that of e-mails, calendar, contacts, tasks through calendar, IIS (webserver) and data storage.

With 2007, they introduced several new features, including:

* Protection (anti-spam, antivirus etc.).
* Extensive Scripting language (Microsoft PowerShell).
* Increased allowed size of database and allowed amount of databases that can be run through Exchange.
* Outlook AnyWhere, a remote access to a web e-mail client.

== Problems I Ran Into and How to Fix ==

I started out on a different network than I was going to end up on, so my DNS had already put in all of the information required for that IP and network. This made everything a bit tricky since my client wouldn't be able to resolve anything as the DNS server is out of reach.

To fix it, I had to reinstall the role DNS server and let it reconfigure itself. Afterwards, everything worked without a hitch.

Trillex small business server 2008

2009-09-25T06:45:26Z

Trillex: /* SharePoint */

Day 4 Tasks: SBS 2008:
--------------------------------
Windows Share Points Services 3?
Share Points Items?
Share Points Roles?
Customizing a Share point Site ?
Windows Exchange Server 2007 theory ?
Distribution group vs Security group ?

= Deployment of Small Business Server 2008 =

THIS IS AN UNDERGOING PROJECT. MOST THINGS, IF NOT ALL, WILL CHANGE DURING THIS WEEK!

IF YOU SEE AN ERROR, CONTACT ME.

== Introduction ==

For this week, I am going to deploy a Small Business Server 2008, that would be suitable for a "standard" business.

Just to give me some kind of aim, I will put up these demands for myself:

The company got 15 computers. They require logins that goes through an exchange server. As any normal company, they also require emails, a website, personal login and a means of getting their files stored remotely on the server. A VPN connection for the workers as well as a means to manage the server remotely could also be mandatory.

=== Introduction to 64 bit Architecture ===

With Windows Server 2008, Microsoft made their operating system 64 bit. This is done for several reasons, but the "main" part of it is that it supports more than 4 GB of memory. They've actually made it mandatory, so you cannot install it without less.

There are more to it, but mostly in memory allocations i.e. larger address spaces, wider registers and data paths. If a 64 bit operating system is handling a 64 bit compiled program or game, it will feel faster in that it got less limitations. This means that the processor can process more data at a time.

== Small Business Server 2008 ==

Microsoft have developed this branch of server operating systems to benefit smaller business that does not require big servers. By doing this, they've made a cheaper license that most business can afford with the ability to update.

=== Features and Components ===

*E-mail Server Application (Through Exchange).
*IIS Server Application. This is essentially a webserver.
*DHCP server
*DNS server
*Active Directory for handling Users and Groups
*Remote Web Workplace, Remote Desktop and VPN support
*Firewall
*Virus Scanner in the form of OneCare.

=== Limitations and Requirements ===

Windows Small Business Server 2008 got certain restrictions. This is because Microsoft wanted this to fit, as the name says, a small business so they put in some limitations to make the server operating system cheaper. Most business will not affected by these limitations. A lot of the limitations, like specific amount of space for emails, can be managed by implanting business policies - such as making sure you keep a tidy email account.

These limitations are:

*Only one SBS server in a domain. The domain can only handle more servers if these are of a different operating system, i.e. like linux, Windows Server etc.
*SBS is very picky about domains. It can only handle one and no child domains.
*Must be the root of the Active Directory forest.
*It is limited to 75 users (licenses).
*Earlier versions of SBS were limited to max 4 GB of memory. SBS 2008 requires a minimum of 4 GB and got a maximum limited of 32 GB. This is due to earlier versions being based on the x86 (32 bit) architecture while 2008 is based on x86-64 (64 bit). This change is because of Exchange Server 2007 is running in 64 bit.
*There are two different versions of SBS 2008. Standard Edition and Premium Edition. The difference between the two are: Premium includes a license to another Windows Server as well as MSSQL database.
*I am not certain if this limitation is still active in 2008 - but in Small Business Server 2003 service pack 2, the Exchange server limits you to 75 GB of emails.

If the business suddenly hits one of these limitations and needs to grow even further, it is possible to upgrade to a bigger license.

=== Installation of Small Server Business 2008 ===

Everybody knows how to press next and fill it out. So I will only fill this out with information that deems necessary to this project.

==== Partitioning ====

Normally, a server will have several harddrives in it and will run a certain kind of raid. Some people like to partition their harddrives to make it more "manageable" because they can assign certain drive letters to specific things, like documents for users etc. This is not at all necessary but can be easier to mange for certain people. I have decided not to do it - simply because it is not needed. By doing it this way, you will also force yourself to "read" drive/folder layouts and optimize them properly. This might be a linux thing but I prefer it this way.

In short, it's a matter of preference.

==== Updating and Virus Protection ====

Throughout the installation, it asks us whether or not we want to keep it up to date with updates and install it's virus scanner. We might as well, eh? Don't do it if you plan on using another one.

==== Post-installation ====

For the love of everything, remove UAC at once. It will make you hate everyone. Do that now.

=== Setting it Up ===

==== Internet Connectivity ====

An important part of a good business network, is having a constant connection to the Internet.

As we do not have a server with two ethernet interfaces, we are forced to do it a different way.

I believe that the best way to do it, is to let the router do the "sharing" and make the server give the IP, gateway and DNS information through it's DHCP server with a standard scope.

As I cannot do this with the current setup, I will not attempt it.

==== Adding Computers to the Domain ====

A pretty nice change in SBS is the ability to add computers. Not only does it add a computer, but it also installs certain tools to make sure that you can monitor a computer without having to physically look at it, i.e. it monitors virus scanner, status, updates etc and gives you a means to log on to it if needed. The way to do this is:

#Have a ready made XP installation. Login as Administrator.
#Go into a webbrowser and go to http://connect - or plug in a USB drive and tell the server to put the necessary files on there
#Follow the simple wizard.

==== Easy Configuration ====

Small Server Business 2008 has taken a hint from the unix world, have truly made it a lot easier to manage users and setting up the system. Upon installation, it starts up and installs the most commonly used services and utilities, such as DNS, IIS, Active Directory and more (These are also called roles and features). But the Windows SBS Console also allows for some amazing wizard options. If you want to add a user, it will automatically create a personal share for it, set the permissions for that folder as well as a "global" shared folder, create an email and send them a default "Welcome" email. Along with this, it can also print out this information. It is sort of a default way to do it, which can be very limiting to some.

While certainly streamlining the general process of managing and monitoring the server and the network, it can get very limiting in certain aspects and if you want to do something that isn't in the SBS Console, you will have to dig it out. If you are not familiar with earlier versions of SBS or Windows Server in general, you could get into a lot of problems doing something that was meant to be easy - like changing DHCP scope options, advanced permissions and logon scripts.

===== Shares =====

As stated above, the installation puts up a very standard, yet functional means of managing and taking care of shares. This is all very good but can be tedious to have to redo, since it just puts it in a standard folder called C:\Users\. If you have several partitions or harddrives, you'd most likely want to make use of them for user shares and documents. Thankfully, it is relatively easy to delete and redo the shares on different folders and is conveniently described in the SBS Console.

It is also with relative ease that you can make sure that it is only certain users who can enter certain directories/shares. It is done in the same way as most 2000+ Windows operating system - but I will just scratch it down quickly; You can do it the time consuming way or you can just add groups that certain people get into. This is all done through the standard Active Directory or can be done through the SBS Console.

I'd personally recommend keeping the sharing structure this way. There aren't many situations where you'd need to create it in a different way. So don't fix what isn't broken.

=== Tools of Small Server Business 2008 ===

Microsoft have expanded a bit on their tools from 2003, most notably Windows SBS Console and Server Manager.

There are 2 different version of Windows SBS Console, normal and advanced mode - though all that advanced does, is add a few extra features under "Tasks".

These two tools cannot really be compared as they are governing two different aspects of the server. While Windows SBS Console is more monitoring, adding of users, shares etc - which is more like every day stuff - the Server Manager is exactly what is said in the name. It manages the server and keeps logs of everything running in the background. Essentially, it is a glorified Event Log as well as a Add/Remove Windows Components - just a lot more advanced in it's features.

Through Server Manager, you can add, remove, start, stop, restart and configure most "roles". Microsoft now call the background things going, i.e. like DNS, DHCP servers "roles". Which makes sense. The things on the frontend of it all, is then called features. These features include tools of varying kind - i.e. for deeper management of every specific role. For example, there are the role called DNS Server and for it, there is a feature called DNS Server Tools. It also has the ability to add "role services" which is essentially a module that can be added to a specific role. An example is that File Services can have a role service called Windows Search Service.

As stated earlier, it is also a event viewer. It keeps track of just about everything that is going on and lists if there has been an error on a specific role or if something has gone horribly wrong - much like what the SBS Console does, except this is deeper - it will show a warning symbol or something else in the main panel and then you can start digging into it.

Obviously, you can find and configure more in details if you go directly to the role/service itself than if you went through SBS Console or Server Manager. Both of them, however, conveniently links to this. A thing to note, is that whatever you add through SBS Console will be added to Active Directory, i.e. users and groups added will be added in it. If you view through Active Directory, you will see these in it's own directory, so you can sort through what changes came from SBS Console.

I am really loving these extra tools, that just makes server monitoring, and to some extend, managing a server a lot easier. Just having a monitor attached to it with SBS Console running constantly will make sure that a lot of errors are caught early on.

=== Remote Web Workplace ===

Again, a great feature from Small Server Business - The Remote Web Workplace is just what it says - a means to connect to work from home and have access to just about everything you need. Intranet website, e-mail and Remote Desktop Connection to any computer you are allowed to. Great for those who wants to clock in some extra hours from home. You can even expand it with Office AnyWhere which provides an online means of viewing, writing and using documents online.

To me, this makes VPN kind of obsolete unless you have a database tool or something that requires you to be connected to a VPN - but that could just as possible be done through Remote Desktop Connection. They still allow for VPN connection but it isn't as simple as with SBS 2003, that even allowed an easy application to be downloaded and used, streamlining the process for workers.

=== Windows Firewall ===

Firewall is, like all the other tools, preinstalled and setup. Firewall in SBS is very tightly integrated with the rest of the systems, which makes sure that the tools that need to go out, gets out and the things that need to go in, goes in.

Obviously, it got a deeper configuration, which can be accessed through the Server Manager tool.
Personally, I feel that this is the way a Firewall should be. When everything that is necessary to make a server/network run is already plotted in, you can just make minor changes and tweaks here and there for whatever you need to make use of.

=== SharePoint ===

SharePoint is a flexible "tool" from Microsoft. Essentially, it is a means to make webpages with ease using a preset form but it is more than that. It can be used as a sort of a file server or a "whiteboard" for work projects, groups and more where the workers can share their work, information etc. It is also a platform for various programs.

As an administrator, you must think it could be hell administering all of the SharePoint items that your business will make use of, but with most things Microsoft, you have a means to give other users group "leadership", so they can add/remove items themselves and generally configure their own item without having to contact their local administrator.

Through SharePoint, users or administrators can create "items" which can contain certain information or a workplan - making it an ideal platform to gather on and keep everybody up to date and synced.

A bit of a downside to SharePoint is that every site you make will, by default, make use of a new port. This means extra adminstration because you have to open up another port, depending if you are using a router or not, for every site you make.

== Network Diagram ==

This network diagram is suited for a very standard small business.

Note that since I do not have access to a computer with two ethernet interfaces, I have made it so I will not require this on the diagram. This can be a problem for certain businesses, since you cannot set up a proper firewall or monitor internet activity etc., except through a router's very limited monitoring tools and firewall. It is, however, possible.

[[Image:Sbs2008.png]]

It can be done in many ways, but this is a pretty good one for what we got.

Remember that this is not how it will look physically.

What we got is a router that connects to the internet. We could have connected the server directly to the router and the switch with it, but that could create a necessary burden on the router - which could strain the network if huge amounts of datas are passed through. You CAN do it but there is no reason to it, if you already got a switch handy. Why would it do this? Well, every packet going to the server would have to go into the inbuilt switch in the router as well as every packet aiming for the web, would have to go through it. Again, you can do it but it is not ideal.

Now that we cleared that up, we got a switch connected to the router. This switch is connected to the server and as many computers there are in the company. Notice that there easily could be more switches in the physical setup, due to computers being spread out in different departments and offices.

=== IP Table ===

{| border="1" class="wikitable"
|-
! IP
! Device
! DHCP or Static
! Gateway
! DNS
|-
| 192.168.1.1/24
| Router
| Static
|
|
|-
| 192.168.1.2/24
| SBS 2008 Server
| Static
|
|
|-
| 192.168.1.10-254/24
| Computers and Devices*
| DHCP
|
|
|}

<nowiki>
* Devices are network printers, IP phones and everything else that would require an IP.
</nowiki>

Pretty straightforward and easy.

=== How to Simulate at Mercantec ===

I do not have access to 15 computers or devices nor do I want to have to set up an entire Cisco Router just for this project, so I cut some corners on certain things but will still accomplish the same thing. I am only writing this here, so I can keep it organized and noted down.

<strike>After consulting Henrik about the network here, he suggested that I just use some IPs freely available here and create it out from that. These two are:</strike>

*<strike>192.168.138.128</strike>
*<strike>192.168.138.131</strike>

<strike>What I will do is give the server the first IP and the computer the second one. Because of this, I cannot install DHCP. I find that installing DHCP is pretty forward anyway and shouldn't need to be documented as we can just assume it is there. It is used for Internet Connectivity section and I will describe it like it is used like that. But if it is needed, let me know and I can find another way to do it.</strike>

After having tried the above, I've decided to just make a small network with just 2 computers in it with no connectivity to the internet. I enabled the scope, I described earlier and set it's gateway and DNS to the fictional router. I've updated both client and server so I shouldn't require any web access.

== Problems I Ran Into and How to Fix ==

I started out on a different network than I was going to end up on, so my DNS had already put in all of the information required for that IP and network. This made everything a bit tricky since my client wouldn't be able to resolve anything as the DNS server is out of reach.

To fix it, I had to reinstall the role DNS server and let it reconfigure itself. Afterwards, everything worked without a hitch.

Trillex small business server 2008

2009-09-25T06:32:52Z

Trillex: /* SharePoint */

Day 4 Tasks: SBS 2008:
--------------------------------
Windows Share Points Services 3?
Share Points Items?
Share Points Roles?
Customizing a Share point Site ?
Windows Exchange Server 2007 theory ?
Distribution group vs Security group ?

= Deployment of Small Business Server 2008 =

THIS IS AN UNDERGOING PROJECT. MOST THINGS, IF NOT ALL, WILL CHANGE DURING THIS WEEK!

IF YOU SEE AN ERROR, CONTACT ME.

== Introduction ==

For this week, I am going to deploy a Small Business Server 2008, that would be suitable for a "standard" business.

Just to give me some kind of aim, I will put up these demands for myself:

The company got 15 computers. They require logins that goes through an exchange server. As any normal company, they also require emails, a website, personal login and a means of getting their files stored remotely on the server. A VPN connection for the workers as well as a means to manage the server remotely could also be mandatory.

=== Introduction to 64 bit Architecture ===

With Windows Server 2008, Microsoft made their operating system 64 bit. This is done for several reasons, but the "main" part of it is that it supports more than 4 GB of memory. They've actually made it mandatory, so you cannot install it without less.

There are more to it, but mostly in memory allocations i.e. larger address spaces, wider registers and data paths. If a 64 bit operating system is handling a 64 bit compiled program or game, it will feel faster in that it got less limitations. This means that the processor can process more data at a time.

== Small Business Server 2008 ==

Microsoft have developed this branch of server operating systems to benefit smaller business that does not require big servers. By doing this, they've made a cheaper license that most business can afford with the ability to update.

=== Features and Components ===

*E-mail Server Application (Through Exchange).
*IIS Server Application. This is essentially a webserver.
*DHCP server
*DNS server
*Active Directory for handling Users and Groups
*Remote Web Workplace, Remote Desktop and VPN support
*Firewall
*Virus Scanner in the form of OneCare.

=== Limitations and Requirements ===

Windows Small Business Server 2008 got certain restrictions. This is because Microsoft wanted this to fit, as the name says, a small business so they put in some limitations to make the server operating system cheaper. Most business will not affected by these limitations. A lot of the limitations, like specific amount of space for emails, can be managed by implanting business policies - such as making sure you keep a tidy email account.

These limitations are:

*Only one SBS server in a domain. The domain can only handle more servers if these are of a different operating system, i.e. like linux, Windows Server etc.
*SBS is very picky about domains. It can only handle one and no child domains.
*Must be the root of the Active Directory forest.
*It is limited to 75 users (licenses).
*Earlier versions of SBS were limited to max 4 GB of memory. SBS 2008 requires a minimum of 4 GB and got a maximum limited of 32 GB. This is due to earlier versions being based on the x86 (32 bit) architecture while 2008 is based on x86-64 (64 bit). This change is because of Exchange Server 2007 is running in 64 bit.
*There are two different versions of SBS 2008. Standard Edition and Premium Edition. The difference between the two are: Premium includes a license to another Windows Server as well as MSSQL database.
*I am not certain if this limitation is still active in 2008 - but in Small Business Server 2003 service pack 2, the Exchange server limits you to 75 GB of emails.

If the business suddenly hits one of these limitations and needs to grow even further, it is possible to upgrade to a bigger license.

=== Installation of Small Server Business 2008 ===

Everybody knows how to press next and fill it out. So I will only fill this out with information that deems necessary to this project.

==== Partitioning ====

Normally, a server will have several harddrives in it and will run a certain kind of raid. Some people like to partition their harddrives to make it more "manageable" because they can assign certain drive letters to specific things, like documents for users etc. This is not at all necessary but can be easier to mange for certain people. I have decided not to do it - simply because it is not needed. By doing it this way, you will also force yourself to "read" drive/folder layouts and optimize them properly. This might be a linux thing but I prefer it this way.

In short, it's a matter of preference.

==== Updating and Virus Protection ====

Throughout the installation, it asks us whether or not we want to keep it up to date with updates and install it's virus scanner. We might as well, eh? Don't do it if you plan on using another one.

==== Post-installation ====

For the love of everything, remove UAC at once. It will make you hate everyone. Do that now.

=== Setting it Up ===

==== Internet Connectivity ====

An important part of a good business network, is having a constant connection to the Internet.

As we do not have a server with two ethernet interfaces, we are forced to do it a different way.

I believe that the best way to do it, is to let the router do the "sharing" and make the server give the IP, gateway and DNS information through it's DHCP server with a standard scope.

As I cannot do this with the current setup, I will not attempt it.

==== Adding Computers to the Domain ====

A pretty nice change in SBS is the ability to add computers. Not only does it add a computer, but it also installs certain tools to make sure that you can monitor a computer without having to physically look at it, i.e. it monitors virus scanner, status, updates etc and gives you a means to log on to it if needed. The way to do this is:

#Have a ready made XP installation. Login as Administrator.
#Go into a webbrowser and go to http://connect - or plug in a USB drive and tell the server to put the necessary files on there
#Follow the simple wizard.

==== Easy Configuration ====

Small Server Business 2008 has taken a hint from the unix world, have truly made it a lot easier to manage users and setting up the system. Upon installation, it starts up and installs the most commonly used services and utilities, such as DNS, IIS, Active Directory and more (These are also called roles and features). But the Windows SBS Console also allows for some amazing wizard options. If you want to add a user, it will automatically create a personal share for it, set the permissions for that folder as well as a "global" shared folder, create an email and send them a default "Welcome" email. Along with this, it can also print out this information. It is sort of a default way to do it, which can be very limiting to some.

While certainly streamlining the general process of managing and monitoring the server and the network, it can get very limiting in certain aspects and if you want to do something that isn't in the SBS Console, you will have to dig it out. If you are not familiar with earlier versions of SBS or Windows Server in general, you could get into a lot of problems doing something that was meant to be easy - like changing DHCP scope options, advanced permissions and logon scripts.

===== Shares =====

As stated above, the installation puts up a very standard, yet functional means of managing and taking care of shares. This is all very good but can be tedious to have to redo, since it just puts it in a standard folder called C:\Users\. If you have several partitions or harddrives, you'd most likely want to make use of them for user shares and documents. Thankfully, it is relatively easy to delete and redo the shares on different folders and is conveniently described in the SBS Console.

It is also with relative ease that you can make sure that it is only certain users who can enter certain directories/shares. It is done in the same way as most 2000+ Windows operating system - but I will just scratch it down quickly; You can do it the time consuming way or you can just add groups that certain people get into. This is all done through the standard Active Directory or can be done through the SBS Console.

I'd personally recommend keeping the sharing structure this way. There aren't many situations where you'd need to create it in a different way. So don't fix what isn't broken.

=== Tools of Small Server Business 2008 ===

Microsoft have expanded a bit on their tools from 2003, most notably Windows SBS Console and Server Manager.

There are 2 different version of Windows SBS Console, normal and advanced mode - though all that advanced does, is add a few extra features under "Tasks".

These two tools cannot really be compared as they are governing two different aspects of the server. While Windows SBS Console is more monitoring, adding of users, shares etc - which is more like every day stuff - the Server Manager is exactly what is said in the name. It manages the server and keeps logs of everything running in the background. Essentially, it is a glorified Event Log as well as a Add/Remove Windows Components - just a lot more advanced in it's features.

Through Server Manager, you can add, remove, start, stop, restart and configure most "roles". Microsoft now call the background things going, i.e. like DNS, DHCP servers "roles". Which makes sense. The things on the frontend of it all, is then called features. These features include tools of varying kind - i.e. for deeper management of every specific role. For example, there are the role called DNS Server and for it, there is a feature called DNS Server Tools. It also has the ability to add "role services" which is essentially a module that can be added to a specific role. An example is that File Services can have a role service called Windows Search Service.

As stated earlier, it is also a event viewer. It keeps track of just about everything that is going on and lists if there has been an error on a specific role or if something has gone horribly wrong - much like what the SBS Console does, except this is deeper - it will show a warning symbol or something else in the main panel and then you can start digging into it.

Obviously, you can find and configure more in details if you go directly to the role/service itself than if you went through SBS Console or Server Manager. Both of them, however, conveniently links to this. A thing to note, is that whatever you add through SBS Console will be added to Active Directory, i.e. users and groups added will be added in it. If you view through Active Directory, you will see these in it's own directory, so you can sort through what changes came from SBS Console.

I am really loving these extra tools, that just makes server monitoring, and to some extend, managing a server a lot easier. Just having a monitor attached to it with SBS Console running constantly will make sure that a lot of errors are caught early on.

=== Remote Web Workplace ===

Again, a great feature from Small Server Business - The Remote Web Workplace is just what it says - a means to connect to work from home and have access to just about everything you need. Intranet website, e-mail and Remote Desktop Connection to any computer you are allowed to. Great for those who wants to clock in some extra hours from home. You can even expand it with Office AnyWhere which provides an online means of viewing, writing and using documents online.

To me, this makes VPN kind of obsolete unless you have a database tool or something that requires you to be connected to a VPN - but that could just as possible be done through Remote Desktop Connection. They still allow for VPN connection but it isn't as simple as with SBS 2003, that even allowed an easy application to be downloaded and used, streamlining the process for workers.

=== Windows Firewall ===

Firewall is, like all the other tools, preinstalled and setup. Firewall in SBS is very tightly integrated with the rest of the systems, which makes sure that the tools that need to go out, gets out and the things that need to go in, goes in.

Obviously, it got a deeper configuration, which can be accessed through the Server Manager tool.
Personally, I feel that this is the way a Firewall should be. When everything that is necessary to make a server/network run is already plotted in, you can just make minor changes and tweaks here and there for whatever you need to make use of.

=== SharePoint ===

SharePoint is a flexible "tool" from Microsoft. Essentially, it is a means to make webpages with ease using a preset form but it is more than that. It can be used as a sort of a file server or a "whiteboard" for work projects, groups and more where the workers can share their work, information etc. It is also a platform for various programs.

As an administrator, you must think it could be hell administering all of the SharePoint items that your business will make use of, but with most things Microsoft, you have a means to give other users group "leadership", so they can add/remove items themselves and generally configure their own item without having to contact their local administrator.

Through SharePoint, users or administrators can create "items" which can contain certain information or a workplan - making it an ideal platform to gather on and keep everybody up to date and synced.

== Network Diagram ==

This network diagram is suited for a very standard small business.

Note that since I do not have access to a computer with two ethernet interfaces, I have made it so I will not require this on the diagram. This can be a problem for certain businesses, since you cannot set up a proper firewall or monitor internet activity etc., except through a router's very limited monitoring tools and firewall. It is, however, possible.

[[Image:Sbs2008.png]]

It can be done in many ways, but this is a pretty good one for what we got.

Remember that this is not how it will look physically.

What we got is a router that connects to the internet. We could have connected the server directly to the router and the switch with it, but that could create a necessary burden on the router - which could strain the network if huge amounts of datas are passed through. You CAN do it but there is no reason to it, if you already got a switch handy. Why would it do this? Well, every packet going to the server would have to go into the inbuilt switch in the router as well as every packet aiming for the web, would have to go through it. Again, you can do it but it is not ideal.

Now that we cleared that up, we got a switch connected to the router. This switch is connected to the server and as many computers there are in the company. Notice that there easily could be more switches in the physical setup, due to computers being spread out in different departments and offices.

=== IP Table ===

{| border="1" class="wikitable"
|-
! IP
! Device
! DHCP or Static
! Gateway
! DNS
|-
| 192.168.1.1/24
| Router
| Static
|
|
|-
| 192.168.1.2/24
| SBS 2008 Server
| Static
|
|
|-
| 192.168.1.10-254/24
| Computers and Devices*
| DHCP
|
|
|}

<nowiki>
* Devices are network printers, IP phones and everything else that would require an IP.
</nowiki>

Pretty straightforward and easy.

=== How to Simulate at Mercantec ===

I do not have access to 15 computers or devices nor do I want to have to set up an entire Cisco Router just for this project, so I cut some corners on certain things but will still accomplish the same thing. I am only writing this here, so I can keep it organized and noted down.

<strike>After consulting Henrik about the network here, he suggested that I just use some IPs freely available here and create it out from that. These two are:</strike>

*<strike>192.168.138.128</strike>
*<strike>192.168.138.131</strike>

<strike>What I will do is give the server the first IP and the computer the second one. Because of this, I cannot install DHCP. I find that installing DHCP is pretty forward anyway and shouldn't need to be documented as we can just assume it is there. It is used for Internet Connectivity section and I will describe it like it is used like that. But if it is needed, let me know and I can find another way to do it.</strike>

After having tried the above, I've decided to just make a small network with just 2 computers in it with no connectivity to the internet. I enabled the scope, I described earlier and set it's gateway and DNS to the fictional router. I've updated both client and server so I shouldn't require any web access.

== Problems I Ran Into and How to Fix ==

I started out on a different network than I was going to end up on, so my DNS had already put in all of the information required for that IP and network. This made everything a bit tricky since my client wouldn't be able to resolve anything as the DNS server is out of reach.

To fix it, I had to reinstall the role DNS server and let it reconfigure itself. Afterwards, everything worked without a hitch.

Trillex - programming in perl with cgi and dbi

2009-09-25T06:28:37Z

Trillex:

[[Category:Linux]][[Category:Perl]][[Category:Projekt]]
= Programming: Perl with Webinterface and Database Injections =
== Introduction ==
As a final project in Perl, I decided to make a script that could be useful as a linux adminstrator. The script is very situational, however, since it makes use of a specific setup.

The idea of the script can be changed and used for many situation, especially when you just need to inject simple things into a table. It certainly beats having to do it manually through that cursed client or through other means like phpmyadmin etc.

What the script does, is add a new user to the database "pureftpd" in the table "ftpd". This is in a MySQL database. The only situation you'd need to do this, is when you have set your FTP daemon up for virtual users, i.e. the user accessing the FTP does not have access to the server itself through SSH, like it would normally if we create another user on most UNIX systems.

== The Script ==
<source lang=perl>
#!/usr/bin/perl
use strict;
use warnings;
use CGI;
use DBI;
use CGI::Carp qw(fatalsToBrowser);

print CGI::header();

my $username = fixtext(CGI::param('user'));
my $status = fixtext(CGI::param('status'));
my $password = fixtext(CGI::param('password'));
my $uid = fixtext(CGI::param('uid'));
my $gid = fixtext(CGI::param('gid'));
my $dir = fixtext(CGI::param('dir'));
my $upload = fixtext(CGI::param('upload'));
my $download = fixtext(CGI::param('download'));
my $comment = fixtext(CGI::param('comment'));
my $ipaccess = fixtext(CGI::param('ipaccess'));
my $quotasize = fixtext(CGI::param('quotasize'));
my $quotafiles = fixtext(CGI::param('quotafiles'));

unless($username) {
print <<PAGE;
<h1>Add a FTP account</h1>
<form action=testadddatabase.pl method=post>
Username: <input type=text name=user><br>
Status: <input type=text name=status><br>
Password: <input type=text name=password><br>
User ID: <input type=text name=uid><br>
Group ID: <input type=text name=gid><br>
Home Dir: <input type=text name=dir><br>
Upload Limit: <input type=text name=upload><br>
Download Limit: <input type=text name=download><br>
Comment: <input type=text name=comment><br>
IP Access: <input type=text name=ipaccess><br>
Quota Size: <input type=text name=quotasize><br>
Quota Files: <input type=text name=quotafiles><br>
<input type=submit value="Add an FTP account">
</form>
PAGE

exit;
}

my $dbh = DBI->connect("dbi:mysql:pureftpd:localhost", "user", "password");

my $sth = $dbh->prepare("insert into ftpd(User, status, Password, Uid, Gid, Dir, ULBandwidth, DLBandwidth, comment, ipaccess, QuotaSize, Quotafiles) values('$username', '$status', '$password', '$uid', '$gid', '$dir', '$upload', '$download', '$comment', '$ipaccess', '$quotasize', '$quotafiles')");

$sth->execute();

print <<PAGE;
<h1>Account added</h1>
The account $username was just added. want to <a href=testadddatabase.pl>add another</a>?
PAGE

sub fixtext {
my ($str) = @_;

$str =~ s/”/\\”/g;
$str =~ s/\\/\\\\/g;
$str =~ s/’/\\’/g;

return $str;
}
</source>

=== Breaking it Down ===

I won't use comments (#) since I will not be able to explain enough in it. I will, hopefully, explain everything here so a newbie can look at it and understand it.

<source lang=perl>
#!/usr/bin/perl
use strict;
use warnings;
use CGI;
use DBI;
use CGI::Carp qw(fatalsToBrowser);
</source>

Essentially this is the start of the script. It tells it what kind of "modules" to make use of. These modules can contain certain functions or be able to give you more information on errors etc.

<source lang=perl>
#!/usr/bin/perl
</source>

What this does is explain that this is now a perl script and it needs to be compiled at /usr/bin/perl. This is, obviously, different on Windows machines and can differ from linux distro.

<source lang=perl>
use strict;
</source>

Strict makes it a bit more "strict" and pretty much slaps you, if you are about to do something nasty in your script that could create a mess. An example is that without strict, you don't have to define variables first but can just write it out. This can cause issues with typos and such, which could lead to strange bugs that will be impossible, or very hard, to find. It's good for beginners.

<source lang=perl>
use warnings;
</source>

Does pretty much what it says. It gives you detailed information if it sees an error in your script when you run it, and outputs it to you. In some situations, it will even tell you exactly what is wrong. Always a good idea to use this, at least for debugging purposes.

<source lang=perl>
use CGI;
</source>

This loads a module for use in CGI, Common Gateway Interface. This is usually used when you want to make web development with perl. It's what making this script work

<source lang=perl>
use DBI;
</source>

Stands for DataBase Interface. Essentially it's the same thing as the CGI, except that it is for database use instead. This can connect, change, view, create databases of various kinds, like SQL, Oracle and more. A very powerful tool.

<source lang=perl>
use CGI::Carp qw(fatalsToBrowser);
</source>

You might have noticed that we have two calls for CGI. This one, however, only calls the functions for Carp with fatalsToBrowser. So to make sure that there is absolutely no chance of messing up, I included a call for normal CGI and then just this one.

<source lang=perl>
print CGI::header();
</source>

What this does, is to define the Content-type in the html code it is going to create through CGI. It essentially makes the script a webpage by defining this.

<source lang=perl>
my $username = fixtext(CGI::param('user'));
my $status = fixtext(CGI::param('status'));
my $password = fixtext(CGI::param('password'));
my $uid = fixtext(CGI::param('uid'));
my $gid = fixtext(CGI::param('gid'));
my $dir = fixtext(CGI::param('dir'));
my $upload = fixtext(CGI::param('upload'));
my $download = fixtext(CGI::param('download'));
my $comment = fixtext(CGI::param('comment'));
my $ipaccess = fixtext(CGI::param('ipaccess'));
my $quotasize = fixtext(CGI::param('quotasize'));
my $quotafiles = fixtext(CGI::param('quotafiles'));
</source>

What this does is define our variables. 'my' "creates" them and the dollar sign ($) defines that it's a variable that will only hold one value. In perl, it is called a scalar. The equal shows it what kind of variable it should be defined with. fixtext is a subroutine, which is explained later. CGI::param'value' will get filled out later on with a value of some kind, through the script. Notice that the "params", the parameters, all have different names. This is what is used in the HTML page. Make sure these add up.

<source lang=perl>
unless($username) {
print <<PAGE;
<h1>Add a FTP account</h1>
<form action=testadddatabase.pl method=post>
Username: <input type=text name=user><br>
Status: <input type=text name=status><br>
Password: <input type=text name=password><br>
User ID: <input type=text name=uid><br>
Group ID: <input type=text name=gid><br>
Home Dir: <input type=text name=dir><br>
Upload Limit: <input type=text name=upload><br>
Download Limit: <input type=text name=download><br>
Comment: <input type=text name=comment><br>
IP Access: <input type=text name=ipaccess><br>
Quota Size: <input type=text name=quotasize><br>
Quota Files: <input type=text name=quotafiles><br>
<input type=submit value="Add an FTP account">
</form>
PAGE

exit;
}
</source>

This creates a website inside the script you are running. This makes it so you don't have to have a HTML page that links to this form. It essentially makes a frontend to the script.

<source lang=perl>
unless($username) {
</source>

This checks what "value" is being passed about. If it already had some information (i.e. the form has already been used), it won't call forth the form. If there is nothing, it will. The "{" starts the "form script" itself.

<source lang=perl>
print <<PAGE;
<h1>Add a FTP account</h1>
<form action=testadddatabase.pl method=post>
Username: <input type=text name=user><br>
Status: <input type=text name=status><br>
Password: <input type=text name=password><br>
User ID: <input type=text name=uid><br>
Group ID: <input type=text name=gid><br>
Home Dir: <input type=text name=dir><br>
Upload Limit: <input type=text name=upload><br>
Download Limit: <input type=text name=download><br>
Comment: <input type=text name=comment><br>
IP Access: <input type=text name=ipaccess><br>
Quota Size: <input type=text name=quotasize><br>
Quota Files: <input type=text name=quotafiles><br>
<input type=submit value="Add an FTP account">
</form>
PAGE

exit;
}
</source>

This creates a webpage inside the script. As you can see, it is just basic HTML code, which points to the script itself so it can run what input the form gives us. Notice that the "name=" refers to something I showed earlier. Exit stops it.

<source lang=perl>
my $dbh = DBI->connect("dbi:mysql:pureftpd:localhost", "user", "password");
</source>

This defines the variable $dbh. It calls the connect function from DBI module. Then makes use of the input in the parenthesis. It goes like this: "DBI:what kind of database:the database's name:host where the database is". User and password is self explanatory.

<source lang=perl>
my $sth = $dbh->prepare("insert into ftpd(User, status, Password, Uid, Gid, Dir, ULBandwidth, DLBandwidth, comment, ipaccess, QuotaSize, Quotafiles) values('$username', '$status', '$password', '$uid', '$gid', '$dir', '$upload', '$download', '$comment', '$ipaccess', '$quotasize', '$quotafiles')");

$sth->execute();
</source>

Defines the variable $sth and then calls $dbh with the added function prepare. This inserts the values from the various variables defined earlier in the script. It inserts it into the table "ftpd".

It then executes all of it. Doing it this way, gives it a better, more readable output to put into the database.

<source lang=perl>
print <<PAGE;
<h1>Account added</h1>
The account $username was just added. want to <a href=testadddatabase.pl>add another</a>?
PAGE
</source>

When the previous have been executed, this creates another website that links to the original script if you want to create another user account.

<source lang=perl>
sub fixtext {
my ($str) = @_;

$str =~ s/”/\\”/g;
$str =~ s/\\/\\\\/g;
$str =~ s/’/\\’/g;

return $str;
}
</source>

This creates a subroutine to a function encountered earlier. What it does, is make sure that there won't be any syntax errors through a simple method of regular expressions (regex). If this wasn't added and someone put in an odd symbol, like " \ / or ', it could wreck the script and add odd things to the database. With this, it adds another \, indicating that this is still a text and not an essential command.

= Conclusion =

This is a basic script but is very powerful, because it simplifies an action that could have taken several minutes. Now it just takes seconds. Imagine what you could do with more advanced scripts.

Trillex small business server 2008

2009-09-25T06:21:16Z

Trillex: /* Windows Firewall */

Day 4 Tasks: SBS 2008:
--------------------------------
Windows Share Points Services 3?
Share Points Items?
Share Points Roles?
Customizing a Share point Site ?
Windows Exchange Server 2007 theory ?
Distribution group vs Security group ?

= Deployment of Small Business Server 2008 =

THIS IS AN UNDERGOING PROJECT. MOST THINGS, IF NOT ALL, WILL CHANGE DURING THIS WEEK!

IF YOU SEE AN ERROR, CONTACT ME.

== Introduction ==

For this week, I am going to deploy a Small Business Server 2008, that would be suitable for a "standard" business.

Just to give me some kind of aim, I will put up these demands for myself:

The company got 15 computers. They require logins that goes through an exchange server. As any normal company, they also require emails, a website, personal login and a means of getting their files stored remotely on the server. A VPN connection for the workers as well as a means to manage the server remotely could also be mandatory.

=== Introduction to 64 bit Architecture ===

With Windows Server 2008, Microsoft made their operating system 64 bit. This is done for several reasons, but the "main" part of it is that it supports more than 4 GB of memory. They've actually made it mandatory, so you cannot install it without less.

There are more to it, but mostly in memory allocations i.e. larger address spaces, wider registers and data paths. If a 64 bit operating system is handling a 64 bit compiled program or game, it will feel faster in that it got less limitations. This means that the processor can process more data at a time.

== Small Business Server 2008 ==

Microsoft have developed this branch of server operating systems to benefit smaller business that does not require big servers. By doing this, they've made a cheaper license that most business can afford with the ability to update.

=== Features and Components ===

*E-mail Server Application (Through Exchange).
*IIS Server Application. This is essentially a webserver.
*DHCP server
*DNS server
*Active Directory for handling Users and Groups
*Remote Web Workplace, Remote Desktop and VPN support
*Firewall
*Virus Scanner in the form of OneCare.

=== Limitations and Requirements ===

Windows Small Business Server 2008 got certain restrictions. This is because Microsoft wanted this to fit, as the name says, a small business so they put in some limitations to make the server operating system cheaper. Most business will not affected by these limitations. A lot of the limitations, like specific amount of space for emails, can be managed by implanting business policies - such as making sure you keep a tidy email account.

These limitations are:

*Only one SBS server in a domain. The domain can only handle more servers if these are of a different operating system, i.e. like linux, Windows Server etc.
*SBS is very picky about domains. It can only handle one and no child domains.
*Must be the root of the Active Directory forest.
*It is limited to 75 users (licenses).
*Earlier versions of SBS were limited to max 4 GB of memory. SBS 2008 requires a minimum of 4 GB and got a maximum limited of 32 GB. This is due to earlier versions being based on the x86 (32 bit) architecture while 2008 is based on x86-64 (64 bit). This change is because of Exchange Server 2007 is running in 64 bit.
*There are two different versions of SBS 2008. Standard Edition and Premium Edition. The difference between the two are: Premium includes a license to another Windows Server as well as MSSQL database.
*I am not certain if this limitation is still active in 2008 - but in Small Business Server 2003 service pack 2, the Exchange server limits you to 75 GB of emails.

If the business suddenly hits one of these limitations and needs to grow even further, it is possible to upgrade to a bigger license.

=== Installation of Small Server Business 2008 ===

Everybody knows how to press next and fill it out. So I will only fill this out with information that deems necessary to this project.

==== Partitioning ====

Normally, a server will have several harddrives in it and will run a certain kind of raid. Some people like to partition their harddrives to make it more "manageable" because they can assign certain drive letters to specific things, like documents for users etc. This is not at all necessary but can be easier to mange for certain people. I have decided not to do it - simply because it is not needed. By doing it this way, you will also force yourself to "read" drive/folder layouts and optimize them properly. This might be a linux thing but I prefer it this way.

In short, it's a matter of preference.

==== Updating and Virus Protection ====

Throughout the installation, it asks us whether or not we want to keep it up to date with updates and install it's virus scanner. We might as well, eh? Don't do it if you plan on using another one.

==== Post-installation ====

For the love of everything, remove UAC at once. It will make you hate everyone. Do that now.

=== Setting it Up ===

==== Internet Connectivity ====

An important part of a good business network, is having a constant connection to the Internet.

As we do not have a server with two ethernet interfaces, we are forced to do it a different way.

I believe that the best way to do it, is to let the router do the "sharing" and make the server give the IP, gateway and DNS information through it's DHCP server with a standard scope.

As I cannot do this with the current setup, I will not attempt it.

==== Adding Computers to the Domain ====

A pretty nice change in SBS is the ability to add computers. Not only does it add a computer, but it also installs certain tools to make sure that you can monitor a computer without having to physically look at it, i.e. it monitors virus scanner, status, updates etc and gives you a means to log on to it if needed. The way to do this is:

#Have a ready made XP installation. Login as Administrator.
#Go into a webbrowser and go to http://connect - or plug in a USB drive and tell the server to put the necessary files on there
#Follow the simple wizard.

==== Easy Configuration ====

Small Server Business 2008 has taken a hint from the unix world, have truly made it a lot easier to manage users and setting up the system. Upon installation, it starts up and installs the most commonly used services and utilities, such as DNS, IIS, Active Directory and more (These are also called roles and features). But the Windows SBS Console also allows for some amazing wizard options. If you want to add a user, it will automatically create a personal share for it, set the permissions for that folder as well as a "global" shared folder, create an email and send them a default "Welcome" email. Along with this, it can also print out this information. It is sort of a default way to do it, which can be very limiting to some.

While certainly streamlining the general process of managing and monitoring the server and the network, it can get very limiting in certain aspects and if you want to do something that isn't in the SBS Console, you will have to dig it out. If you are not familiar with earlier versions of SBS or Windows Server in general, you could get into a lot of problems doing something that was meant to be easy - like changing DHCP scope options, advanced permissions and logon scripts.

===== Shares =====

As stated above, the installation puts up a very standard, yet functional means of managing and taking care of shares. This is all very good but can be tedious to have to redo, since it just puts it in a standard folder called C:\Users\. If you have several partitions or harddrives, you'd most likely want to make use of them for user shares and documents. Thankfully, it is relatively easy to delete and redo the shares on different folders and is conveniently described in the SBS Console.

It is also with relative ease that you can make sure that it is only certain users who can enter certain directories/shares. It is done in the same way as most 2000+ Windows operating system - but I will just scratch it down quickly; You can do it the time consuming way or you can just add groups that certain people get into. This is all done through the standard Active Directory or can be done through the SBS Console.

I'd personally recommend keeping the sharing structure this way. There aren't many situations where you'd need to create it in a different way. So don't fix what isn't broken.

=== Tools of Small Server Business 2008 ===

Microsoft have expanded a bit on their tools from 2003, most notably Windows SBS Console and Server Manager.

There are 2 different version of Windows SBS Console, normal and advanced mode - though all that advanced does, is add a few extra features under "Tasks".

These two tools cannot really be compared as they are governing two different aspects of the server. While Windows SBS Console is more monitoring, adding of users, shares etc - which is more like every day stuff - the Server Manager is exactly what is said in the name. It manages the server and keeps logs of everything running in the background. Essentially, it is a glorified Event Log as well as a Add/Remove Windows Components - just a lot more advanced in it's features.

Through Server Manager, you can add, remove, start, stop, restart and configure most "roles". Microsoft now call the background things going, i.e. like DNS, DHCP servers "roles". Which makes sense. The things on the frontend of it all, is then called features. These features include tools of varying kind - i.e. for deeper management of every specific role. For example, there are the role called DNS Server and for it, there is a feature called DNS Server Tools. It also has the ability to add "role services" which is essentially a module that can be added to a specific role. An example is that File Services can have a role service called Windows Search Service.

As stated earlier, it is also a event viewer. It keeps track of just about everything that is going on and lists if there has been an error on a specific role or if something has gone horribly wrong - much like what the SBS Console does, except this is deeper - it will show a warning symbol or something else in the main panel and then you can start digging into it.

Obviously, you can find and configure more in details if you go directly to the role/service itself than if you went through SBS Console or Server Manager. Both of them, however, conveniently links to this. A thing to note, is that whatever you add through SBS Console will be added to Active Directory, i.e. users and groups added will be added in it. If you view through Active Directory, you will see these in it's own directory, so you can sort through what changes came from SBS Console.

I am really loving these extra tools, that just makes server monitoring, and to some extend, managing a server a lot easier. Just having a monitor attached to it with SBS Console running constantly will make sure that a lot of errors are caught early on.

=== Remote Web Workplace ===

Again, a great feature from Small Server Business - The Remote Web Workplace is just what it says - a means to connect to work from home and have access to just about everything you need. Intranet website, e-mail and Remote Desktop Connection to any computer you are allowed to. Great for those who wants to clock in some extra hours from home. You can even expand it with Office AnyWhere which provides an online means of viewing, writing and using documents online.

To me, this makes VPN kind of obsolete unless you have a database tool or something that requires you to be connected to a VPN - but that could just as possible be done through Remote Desktop Connection. They still allow for VPN connection but it isn't as simple as with SBS 2003, that even allowed an easy application to be downloaded and used, streamlining the process for workers.

=== Windows Firewall ===

Firewall is, like all the other tools, preinstalled and setup. Firewall in SBS is very tightly integrated with the rest of the systems, which makes sure that the tools that need to go out, gets out and the things that need to go in, goes in.

Obviously, it got a deeper configuration, which can be accessed through the Server Manager tool.
Personally, I feel that this is the way a Firewall should be. When everything that is necessary to make a server/network run is already plotted in, you can just make minor changes and tweaks here and there for whatever you need to make use of.

=== SharePoint ===

SharePoint is a flexible "tool" from Microsoft. Essentially, it is a means to make webpages with ease using a preset form but it is more than that. It can be used as a sort of a file server or a "whiteboard" for work projects, groups and more where the workers can share their work, information etc. It is also a platform for various programs.

Through SharePoint, users or administrators can create "items" which can contain certain information or a workplan - making it an ideal platform to gather on and keep everybody up to date and synced.

== Network Diagram ==

This network diagram is suited for a very standard small business.

Note that since I do not have access to a computer with two ethernet interfaces, I have made it so I will not require this on the diagram. This can be a problem for certain businesses, since you cannot set up a proper firewall or monitor internet activity etc., except through a router's very limited monitoring tools and firewall. It is, however, possible.

[[Image:Sbs2008.png]]

It can be done in many ways, but this is a pretty good one for what we got.

Remember that this is not how it will look physically.

What we got is a router that connects to the internet. We could have connected the server directly to the router and the switch with it, but that could create a necessary burden on the router - which could strain the network if huge amounts of datas are passed through. You CAN do it but there is no reason to it, if you already got a switch handy. Why would it do this? Well, every packet going to the server would have to go into the inbuilt switch in the router as well as every packet aiming for the web, would have to go through it. Again, you can do it but it is not ideal.

Now that we cleared that up, we got a switch connected to the router. This switch is connected to the server and as many computers there are in the company. Notice that there easily could be more switches in the physical setup, due to computers being spread out in different departments and offices.

=== IP Table ===

{| border="1" class="wikitable"
|-
! IP
! Device
! DHCP or Static
! Gateway
! DNS
|-
| 192.168.1.1/24
| Router
| Static
|
|
|-
| 192.168.1.2/24
| SBS 2008 Server
| Static
|
|
|-
| 192.168.1.10-254/24
| Computers and Devices*
| DHCP
|
|
|}

<nowiki>
* Devices are network printers, IP phones and everything else that would require an IP.
</nowiki>

Pretty straightforward and easy.

=== How to Simulate at Mercantec ===

I do not have access to 15 computers or devices nor do I want to have to set up an entire Cisco Router just for this project, so I cut some corners on certain things but will still accomplish the same thing. I am only writing this here, so I can keep it organized and noted down.

<strike>After consulting Henrik about the network here, he suggested that I just use some IPs freely available here and create it out from that. These two are:</strike>

*<strike>192.168.138.128</strike>
*<strike>192.168.138.131</strike>

<strike>What I will do is give the server the first IP and the computer the second one. Because of this, I cannot install DHCP. I find that installing DHCP is pretty forward anyway and shouldn't need to be documented as we can just assume it is there. It is used for Internet Connectivity section and I will describe it like it is used like that. But if it is needed, let me know and I can find another way to do it.</strike>

After having tried the above, I've decided to just make a small network with just 2 computers in it with no connectivity to the internet. I enabled the scope, I described earlier and set it's gateway and DNS to the fictional router. I've updated both client and server so I shouldn't require any web access.

== Problems I Ran Into and How to Fix ==

I started out on a different network than I was going to end up on, so my DNS had already put in all of the information required for that IP and network. This made everything a bit tricky since my client wouldn't be able to resolve anything as the DNS server is out of reach.

To fix it, I had to reinstall the role DNS server and let it reconfigure itself. Afterwards, everything worked without a hitch.

Trillex small business server 2008

2009-09-24T23:16:26Z

Trillex:

Day 4 Tasks: SBS 2008:
--------------------------------
Windows Share Points Services 3?
Share Points Items?
Share Points Roles?
Customizing a Share point Site ?
Windows Exchange Server 2007 theory ?
Distribution group vs Security group ?

= Deployment of Small Business Server 2008 =

THIS IS AN UNDERGOING PROJECT. MOST THINGS, IF NOT ALL, WILL CHANGE DURING THIS WEEK!

IF YOU SEE AN ERROR, CONTACT ME.

== Introduction ==

For this week, I am going to deploy a Small Business Server 2008, that would be suitable for a "standard" business.

Just to give me some kind of aim, I will put up these demands for myself:

The company got 15 computers. They require logins that goes through an exchange server. As any normal company, they also require emails, a website, personal login and a means of getting their files stored remotely on the server. A VPN connection for the workers as well as a means to manage the server remotely could also be mandatory.

=== Introduction to 64 bit Architecture ===

With Windows Server 2008, Microsoft made their operating system 64 bit. This is done for several reasons, but the "main" part of it is that it supports more than 4 GB of memory. They've actually made it mandatory, so you cannot install it without less.

There are more to it, but mostly in memory allocations i.e. larger address spaces, wider registers and data paths. If a 64 bit operating system is handling a 64 bit compiled program or game, it will feel faster in that it got less limitations. This means that the processor can process more data at a time.

== Small Business Server 2008 ==

Microsoft have developed this branch of server operating systems to benefit smaller business that does not require big servers. By doing this, they've made a cheaper license that most business can afford with the ability to update.

=== Features and Components ===

*E-mail Server Application (Through Exchange).
*IIS Server Application. This is essentially a webserver.
*DHCP server
*DNS server
*Active Directory for handling Users and Groups
*Remote Web Workplace, Remote Desktop and VPN support
*Firewall
*Virus Scanner in the form of OneCare.

=== Limitations and Requirements ===

Windows Small Business Server 2008 got certain restrictions. This is because Microsoft wanted this to fit, as the name says, a small business so they put in some limitations to make the server operating system cheaper. Most business will not affected by these limitations. A lot of the limitations, like specific amount of space for emails, can be managed by implanting business policies - such as making sure you keep a tidy email account.

These limitations are:

*Only one SBS server in a domain. The domain can only handle more servers if these are of a different operating system, i.e. like linux, Windows Server etc.
*SBS is very picky about domains. It can only handle one and no child domains.
*Must be the root of the Active Directory forest.
*It is limited to 75 users (licenses).
*Earlier versions of SBS were limited to max 4 GB of memory. SBS 2008 requires a minimum of 4 GB and got a maximum limited of 32 GB. This is due to earlier versions being based on the x86 (32 bit) architecture while 2008 is based on x86-64 (64 bit). This change is because of Exchange Server 2007 is running in 64 bit.
*There are two different versions of SBS 2008. Standard Edition and Premium Edition. The difference between the two are: Premium includes a license to another Windows Server as well as MSSQL database.
*I am not certain if this limitation is still active in 2008 - but in Small Business Server 2003 service pack 2, the Exchange server limits you to 75 GB of emails.

If the business suddenly hits one of these limitations and needs to grow even further, it is possible to upgrade to a bigger license.

=== Installation of Small Server Business 2008 ===

Everybody knows how to press next and fill it out. So I will only fill this out with information that deems necessary to this project.

==== Partitioning ====

Normally, a server will have several harddrives in it and will run a certain kind of raid. Some people like to partition their harddrives to make it more "manageable" because they can assign certain drive letters to specific things, like documents for users etc. This is not at all necessary but can be easier to mange for certain people. I have decided not to do it - simply because it is not needed. By doing it this way, you will also force yourself to "read" drive/folder layouts and optimize them properly. This might be a linux thing but I prefer it this way.

In short, it's a matter of preference.

==== Updating and Virus Protection ====

Throughout the installation, it asks us whether or not we want to keep it up to date with updates and install it's virus scanner. We might as well, eh? Don't do it if you plan on using another one.

==== Post-installation ====

For the love of everything, remove UAC at once. It will make you hate everyone. Do that now.

=== Setting it Up ===

==== Internet Connectivity ====

An important part of a good business network, is having a constant connection to the Internet.

As we do not have a server with two ethernet interfaces, we are forced to do it a different way.

I believe that the best way to do it, is to let the router do the "sharing" and make the server give the IP, gateway and DNS information through it's DHCP server with a standard scope.

As I cannot do this with the current setup, I will not attempt it.

==== Adding Computers to the Domain ====

A pretty nice change in SBS is the ability to add computers. Not only does it add a computer, but it also installs certain tools to make sure that you can monitor a computer without having to physically look at it, i.e. it monitors virus scanner, status, updates etc and gives you a means to log on to it if needed. The way to do this is:

#Have a ready made XP installation. Login as Administrator.
#Go into a webbrowser and go to http://connect - or plug in a USB drive and tell the server to put the necessary files on there
#Follow the simple wizard.

==== Easy Configuration ====

Small Server Business 2008 has taken a hint from the unix world, have truly made it a lot easier to manage users and setting up the system. Upon installation, it starts up and installs the most commonly used services and utilities, such as DNS, IIS, Active Directory and more (These are also called roles and features). But the Windows SBS Console also allows for some amazing wizard options. If you want to add a user, it will automatically create a personal share for it, set the permissions for that folder as well as a "global" shared folder, create an email and send them a default "Welcome" email. Along with this, it can also print out this information. It is sort of a default way to do it, which can be very limiting to some.

While certainly streamlining the general process of managing and monitoring the server and the network, it can get very limiting in certain aspects and if you want to do something that isn't in the SBS Console, you will have to dig it out. If you are not familiar with earlier versions of SBS or Windows Server in general, you could get into a lot of problems doing something that was meant to be easy - like changing DHCP scope options, advanced permissions and logon scripts.

===== Shares =====

As stated above, the installation puts up a very standard, yet functional means of managing and taking care of shares. This is all very good but can be tedious to have to redo, since it just puts it in a standard folder called C:\Users\. If you have several partitions or harddrives, you'd most likely want to make use of them for user shares and documents. Thankfully, it is relatively easy to delete and redo the shares on different folders and is conveniently described in the SBS Console.

It is also with relative ease that you can make sure that it is only certain users who can enter certain directories/shares. It is done in the same way as most 2000+ Windows operating system - but I will just scratch it down quickly; You can do it the time consuming way or you can just add groups that certain people get into. This is all done through the standard Active Directory or can be done through the SBS Console.

I'd personally recommend keeping the sharing structure this way. There aren't many situations where you'd need to create it in a different way. So don't fix what isn't broken.

=== Tools of Small Server Business 2008 ===

Microsoft have expanded a bit on their tools from 2003, most notably Windows SBS Console and Server Manager.

There are 2 different version of Windows SBS Console, normal and advanced mode - though all that advanced does, is add a few extra features under "Tasks".

These two tools cannot really be compared as they are governing two different aspects of the server. While Windows SBS Console is more monitoring, adding of users, shares etc - which is more like every day stuff - the Server Manager is exactly what is said in the name. It manages the server and keeps logs of everything running in the background. Essentially, it is a glorified Event Log as well as a Add/Remove Windows Components - just a lot more advanced in it's features.

Through Server Manager, you can add, remove, start, stop, restart and configure most "roles". Microsoft now call the background things going, i.e. like DNS, DHCP servers "roles". Which makes sense. The things on the frontend of it all, is then called features. These features include tools of varying kind - i.e. for deeper management of every specific role. For example, there are the role called DNS Server and for it, there is a feature called DNS Server Tools. It also has the ability to add "role services" which is essentially a module that can be added to a specific role. An example is that File Services can have a role service called Windows Search Service.

As stated earlier, it is also a event viewer. It keeps track of just about everything that is going on and lists if there has been an error on a specific role or if something has gone horribly wrong - much like what the SBS Console does, except this is deeper - it will show a warning symbol or something else in the main panel and then you can start digging into it.

Obviously, you can find and configure more in details if you go directly to the role/service itself than if you went through SBS Console or Server Manager. Both of them, however, conveniently links to this. A thing to note, is that whatever you add through SBS Console will be added to Active Directory, i.e. users and groups added will be added in it. If you view through Active Directory, you will see these in it's own directory, so you can sort through what changes came from SBS Console.

I am really loving these extra tools, that just makes server monitoring, and to some extend, managing a server a lot easier. Just having a monitor attached to it with SBS Console running constantly will make sure that a lot of errors are caught early on.

=== Remote Web Workplace ===

Again, a great feature from Small Server Business - The Remote Web Workplace is just what it says - a means to connect to work from home and have access to just about everything you need. Intranet website, e-mail and Remote Desktop Connection to any computer you are allowed to. Great for those who wants to clock in some extra hours from home. You can even expand it with Office AnyWhere which provides an online means of viewing, writing and using documents online.

To me, this makes VPN kind of obsolete unless you have a database tool or something that requires you to be connected to a VPN - but that could just as possible be done through Remote Desktop Connection. They still allow for VPN connection but it isn't as simple as with SBS 2003, that even allowed an easy application to be downloaded and used, streamlining the process for workers.

=== Windows Firewall ===

Firewall is, like all the other tools, preinstalled and setup. Firewall in SBS is very tightly integrated with the rest of the systems, which makes sure that the tools that need to go out, gets out and the things that need to go in, goes in.

Obviously, it got a deeper configuration, which can be accessed through the Server Manager tool.
Personally, I feel that this is the way a Firewall should be. When everything that is necessary to make a server/network run is already plotted in, you can just make minor changes and tweaks here and there for whatever you need to make use of.

== Network Diagram ==

This network diagram is suited for a very standard small business.

Note that since I do not have access to a computer with two ethernet interfaces, I have made it so I will not require this on the diagram. This can be a problem for certain businesses, since you cannot set up a proper firewall or monitor internet activity etc., except through a router's very limited monitoring tools and firewall. It is, however, possible.

[[Image:Sbs2008.png]]

It can be done in many ways, but this is a pretty good one for what we got.

Remember that this is not how it will look physically.

What we got is a router that connects to the internet. We could have connected the server directly to the router and the switch with it, but that could create a necessary burden on the router - which could strain the network if huge amounts of datas are passed through. You CAN do it but there is no reason to it, if you already got a switch handy. Why would it do this? Well, every packet going to the server would have to go into the inbuilt switch in the router as well as every packet aiming for the web, would have to go through it. Again, you can do it but it is not ideal.

Now that we cleared that up, we got a switch connected to the router. This switch is connected to the server and as many computers there are in the company. Notice that there easily could be more switches in the physical setup, due to computers being spread out in different departments and offices.

=== IP Table ===

{| border="1" class="wikitable"
|-
! IP
! Device
! DHCP or Static
! Gateway
! DNS
|-
| 192.168.1.1/24
| Router
| Static
|
|
|-
| 192.168.1.2/24
| SBS 2008 Server
| Static
|
|
|-
| 192.168.1.10-254/24
| Computers and Devices*
| DHCP
|
|
|}

<nowiki>
* Devices are network printers, IP phones and everything else that would require an IP.
</nowiki>

Pretty straightforward and easy.

=== How to Simulate at Mercantec ===

I do not have access to 15 computers or devices nor do I want to have to set up an entire Cisco Router just for this project, so I cut some corners on certain things but will still accomplish the same thing. I am only writing this here, so I can keep it organized and noted down.

<strike>After consulting Henrik about the network here, he suggested that I just use some IPs freely available here and create it out from that. These two are:</strike>

*<strike>192.168.138.128</strike>
*<strike>192.168.138.131</strike>

<strike>What I will do is give the server the first IP and the computer the second one. Because of this, I cannot install DHCP. I find that installing DHCP is pretty forward anyway and shouldn't need to be documented as we can just assume it is there. It is used for Internet Connectivity section and I will describe it like it is used like that. But if it is needed, let me know and I can find another way to do it.</strike>

After having tried the above, I've decided to just make a small network with just 2 computers in it with no connectivity to the internet. I enabled the scope, I described earlier and set it's gateway and DNS to the fictional router. I've updated both client and server so I shouldn't require any web access.

== Problems I Ran Into and How to Fix ==

I started out on a different network than I was going to end up on, so my DNS had already put in all of the information required for that IP and network. This made everything a bit tricky since my client wouldn't be able to resolve anything as the DNS server is out of reach.

To fix it, I had to reinstall the role DNS server and let it reconfigure itself. Afterwards, everything worked without a hitch.

Trillex small business server 2008

2009-09-23T12:03:16Z

Trillex: /* Tools of Small Server Business 2008 */

= Deployment of Small Business Server 2008 =

THIS IS AN UNDERGOING PROJECT. MOST THINGS, IF NOT ALL, WILL CHANGE DURING THIS WEEK!

IF YOU SEE AN ERROR, CONTACT ME.

== Introduction ==

For this week, I am going to deploy a Small Business Server 2008, that would be suitable for a "standard" business.

Just to give me some kind of aim, I will put up these demands for myself:

The company got 15 computers. They require logins that goes through an exchange server. As any normal company, they also require emails, a website, personal login and a means of getting their files stored remotely on the server. A VPN connection for the workers as well as a means to manage the server remotely could also be mandatory.

=== Introduction to 64 bit Architecture ===

With Windows Server 2008, Microsoft made their operating system 64 bit. This is done for several reasons, but the "main" part of it is that it supports more than 4 GB of memory. They've actually made it mandatory, so you cannot install it without less.

There are more to it, but mostly in memory allocations i.e. larger address spaces, wider registers and data paths. If a 64 bit operating system is handling a 64 bit compiled program or game, it will feel faster in that it got less limitations. This means that the processor can process more data at a time.

== Small Business Server 2008 ==

Microsoft have developed this branch of server operating systems to benefit smaller business that does not require big servers. By doing this, they've made a cheaper license that most business can afford with the ability to update.

=== Features and Components ===

*E-mail Server Application (Through Exchange).
*IIS Server Application. This is essentially a webserver.
*DHCP server
*DNS server
*Active Directory for handling Users and Groups
*Remote Web Workplace, Remote Desktop and VPN support
*Firewall
*Virus Scanner in the form of OneCare.

=== Limitations and Requirements ===

Windows Small Business Server 2008 got certain restrictions. This is because Microsoft wanted this to fit, as the name says, a small business so they put in some limitations to make the server operating system cheaper. Most business will not affected by these limitations. A lot of the limitations, like specific amount of space for emails, can be managed by implanting business policies - such as making sure you keep a tidy email account.

These limitations are:

*Only one SBS server in a domain. The domain can only handle more servers if these are of a different operating system, i.e. like linux, Windows Server etc.
*SBS is very picky about domains. It can only handle one and no child domains.
*Must be the root of the Active Directory forest.
*It is limited to 75 users (licenses).
*Earlier versions of SBS were limited to max 4 GB of memory. SBS 2008 requires a minimum of 4 GB and got a maximum limited of 32 GB. This is due to earlier versions being based on the x86 (32 bit) architecture while 2008 is based on x86-64 (64 bit). This change is because of Exchange Server 2007 is running in 64 bit.
*There are two different versions of SBS 2008. Standard Edition and Premium Edition. The difference between the two are: Premium includes a license to another Windows Server as well as MSSQL database.
*I am not certain if this limitation is still active in 2008 - but in Small Business Server 2003 service pack 2, the Exchange server limits you to 75 GB of emails.

If the business suddenly hits one of these limitations and needs to grow even further, it is possible to upgrade to a bigger license.

=== Installation of Small Server Business 2008 ===

Everybody knows how to press next and fill it out. So I will only fill this out with information that deems necessary to this project.

==== Partitioning ====

Normally, a server will have several harddrives in it and will run a certain kind of raid. Some people like to partition their harddrives to make it more "manageable" because they can assign certain drive letters to specific things, like documents for users etc. This is not at all necessary but can be easier to mange for certain people. I have decided not to do it - simply because it is not needed. By doing it this way, you will also force yourself to "read" drive/folder layouts and optimize them properly. This might be a linux thing but I prefer it this way.

In short, it's a matter of preference.

==== Updating and Virus Protection ====

Throughout the installation, it asks us whether or not we want to keep it up to date with updates and install it's virus scanner. We might as well, eh? Don't do it if you plan on using another one.

==== Post-installation ====

For the love of everything, remove UAC at once. It will make you hate everyone. Do that now.

=== Setting it Up ===

==== Internet Connectivity ====

An important part of a good business network, is having a constant connection to the Internet.

As we do not have a server with two ethernet interfaces, we are forced to do it a different way.

I believe that the best way to do it, is to let the router do the "sharing" and make the server give the IP, gateway and DNS information through it's DHCP server with a standard scope.

As I cannot do this with the current setup, I will not attempt it.

==== Adding Computers to the Domain ====

A pretty nice change in SBS is the ability to add computers. Not only does it add a computer, but it also installs certain tools to make sure that you can monitor a computer without having to physically look at it, i.e. it monitors virus scanner, status, updates etc and gives you a means to log on to it if needed. The way to do this is:

#Have a ready made XP installation. Login as Administrator.
#Go into a webbrowser and go to http://connect - or plug in a USB drive and tell the server to put the necessary files on there
#Follow the simple wizard.

==== Easy Configuration ====

Small Server Business 2008 has taken a hint from the unix world, have truly made it a lot easier to manage users and setting up the system. Upon installation, it starts up and installs the most commonly used services and utilities, such as DNS, IIS, Active Directory and more (These are also called roles and features). But the Windows SBS Console also allows for some amazing wizard options. If you want to add a user, it will automatically create a personal share for it, set the permissions for that folder as well as a "global" shared folder, create an email and send them a default "Welcome" email. Along with this, it can also print out this information. It is sort of a default way to do it, which can be very limiting to some.

While certainly streamlining the general process of managing and monitoring the server and the network, it can get very limiting in certain aspects and if you want to do something that isn't in the SBS Console, you will have to dig it out. If you are not familiar with earlier versions of SBS or Windows Server in general, you could get into a lot of problems doing something that was meant to be easy - like changing DHCP scope options, advanced permissions and logon scripts.

===== Shares =====

As stated above, the installation puts up a very standard, yet functional means of managing and taking care of shares. This is all very good but can be tedious to have to redo, since it just puts it in a standard folder called C:\Users\. If you have several partitions or harddrives, you'd most likely want to make use of them for user shares and documents. Thankfully, it is relatively easy to delete and redo the shares on different folders and is conveniently described in the SBS Console.

It is also with relative ease that you can make sure that it is only certain users who can enter certain directories/shares. It is done in the same way as most 2000+ Windows operating system - but I will just scratch it down quickly; You can do it the time consuming way or you can just add groups that certain people get into. This is all done through the standard Active Directory or can be done through the SBS Console.

I'd personally recommend keeping the sharing structure this way. There aren't many situations where you'd need to create it in a different way. So don't fix what isn't broken.

=== Tools of Small Server Business 2008 ===

Microsoft have expanded a bit on their tools from 2003, most notably Windows SBS Console and Server Manager.

There are 2 different version of Windows SBS Console, normal and advanced mode - though all that advanced does, is add a few extra features under "Tasks".

These two tools cannot really be compared as they are governing two different aspects of the server. While Windows SBS Console is more monitoring, adding of users, shares etc - which is more like every day stuff - the Server Manager is exactly what is said in the name. It manages the server and keeps logs of everything running in the background. Essentially, it is a glorified Event Log as well as a Add/Remove Windows Components - just a lot more advanced in it's features.

Through Server Manager, you can add, remove, start, stop, restart and configure most "roles". Microsoft now call the background things going, i.e. like DNS, DHCP servers "roles". Which makes sense. The things on the frontend of it all, is then called features. These features include tools of varying kind - i.e. for deeper management of every specific role. For example, there are the role called DNS Server and for it, there is a feature called DNS Server Tools. It also has the ability to add "role services" which is essentially a module that can be added to a specific role. An example is that File Services can have a role service called Windows Search Service.

As stated earlier, it is also a event viewer. It keeps track of just about everything that is going on and lists if there has been an error on a specific role or if something has gone horribly wrong - much like what the SBS Console does, except this is deeper - it will show a warning symbol or something else in the main panel and then you can start digging into it.

Obviously, you can find and configure more in details if you go directly to the role/service itself than if you went through SBS Console or Server Manager. Both of them, however, conveniently links to this. A thing to note, is that whatever you add through SBS Console will be added to Active Directory, i.e. users and groups added will be added in it. If you view through Active Directory, you will see these in it's own directory, so you can sort through what changes came from SBS Console.

I am really loving these extra tools, that just makes server monitoring, and to some extend, managing a server a lot easier. Just having a monitor attached to it with SBS Console running constantly will make sure that a lot of errors are caught early on.

=== Remote Web Workplace ===

Again, a great feature from Small Server Business - The Remote Web Workplace is just what it says - a means to connect to work from home and have access to just about everything you need. Intranet website, e-mail and Remote Desktop Connection to any computer you are allowed to. Great for those who wants to clock in some extra hours from home. You can even expand it with Office AnyWhere which provides an online means of viewing, writing and using documents online.

To me, this makes VPN kind of obsolete unless you have a database tool or something that requires you to be connected to a VPN - but that could just as possible be done through Remote Desktop Connection. They still allow for VPN connection but it isn't as simple as with SBS 2003, that even allowed an easy application to be downloaded and used, streamlining the process for workers.

=== Windows Firewall ===

Firewall is, like all the other tools, preinstalled and setup. Firewall in SBS is very tightly integrated with the rest of the systems, which makes sure that the tools that need to go out, gets out and the things that need to go in, goes in.

Obviously, it got a deeper configuration, which can be accessed through the Server Manager tool.
Personally, I feel that this is the way a Firewall should be. When everything that is necessary to make a server/network run is already plotted in, you can just make minor changes and tweaks here and there for whatever you need to make use of.

== Network Diagram ==

This network diagram is suited for a very standard small business.

Note that since I do not have access to a computer with two ethernet interfaces, I have made it so I will not require this on the diagram. This can be a problem for certain businesses, since you cannot set up a proper firewall or monitor internet activity etc., except through a router's very limited monitoring tools and firewall. It is, however, possible.

[[Image:Sbs2008.png]]

It can be done in many ways, but this is a pretty good one for what we got.

Remember that this is not how it will look physically.

What we got is a router that connects to the internet. We could have connected the server directly to the router and the switch with it, but that could create a necessary burden on the router - which could strain the network if huge amounts of datas are passed through. You CAN do it but there is no reason to it, if you already got a switch handy. Why would it do this? Well, every packet going to the server would have to go into the inbuilt switch in the router as well as every packet aiming for the web, would have to go through it. Again, you can do it but it is not ideal.

Now that we cleared that up, we got a switch connected to the router. This switch is connected to the server and as many computers there are in the company. Notice that there easily could be more switches in the physical setup, due to computers being spread out in different departments and offices.

=== IP Table ===

{| border="1" class="wikitable"
|-
! IP
! Device
! DHCP or Static
! Gateway
! DNS
|-
| 192.168.1.1/24
| Router
| Static
|
|
|-
| 192.168.1.2/24
| SBS 2008 Server
| Static
|
|
|-
| 192.168.1.10-254/24
| Computers and Devices*
| DHCP
|
|
|}

<nowiki>
* Devices are network printers, IP phones and everything else that would require an IP.
</nowiki>

Pretty straightforward and easy.

=== How to Simulate at Mercantec ===

I do not have access to 15 computers or devices nor do I want to have to set up an entire Cisco Router just for this project, so I cut some corners on certain things but will still accomplish the same thing. I am only writing this here, so I can keep it organized and noted down.

<strike>After consulting Henrik about the network here, he suggested that I just use some IPs freely available here and create it out from that. These two are:</strike>

*<strike>192.168.138.128</strike>
*<strike>192.168.138.131</strike>

<strike>What I will do is give the server the first IP and the computer the second one. Because of this, I cannot install DHCP. I find that installing DHCP is pretty forward anyway and shouldn't need to be documented as we can just assume it is there. It is used for Internet Connectivity section and I will describe it like it is used like that. But if it is needed, let me know and I can find another way to do it.</strike>

After having tried the above, I've decided to just make a small network with just 2 computers in it with no connectivity to the internet. I enabled the scope, I described earlier and set it's gateway and DNS to the fictional router. I've updated both client and server so I shouldn't require any web access.

== Problems I Ran Into and How to Fix ==

I started out on a different network than I was going to end up on, so my DNS had already put in all of the information required for that IP and network. This made everything a bit tricky since my client wouldn't be able to resolve anything as the DNS server is out of reach.

To fix it, I had to reinstall the role DNS server and let it reconfigure itself. Afterwards, everything worked without a hitch.

Trillex small business server 2008

2009-09-23T11:01:16Z

Trillex: /* Tools of Small Server Business 2008 */

= Deployment of Small Business Server 2008 =

THIS IS AN UNDERGOING PROJECT. MOST THINGS, IF NOT ALL, WILL CHANGE DURING THIS WEEK!

IF YOU SEE AN ERROR, CONTACT ME.

== Introduction ==

For this week, I am going to deploy a Small Business Server 2008, that would be suitable for a "standard" business.

Just to give me some kind of aim, I will put up these demands for myself:

The company got 15 computers. They require logins that goes through an exchange server. As any normal company, they also require emails, a website, personal login and a means of getting their files stored remotely on the server. A VPN connection for the workers as well as a means to manage the server remotely could also be mandatory.

=== Introduction to 64 bit Architecture ===

With Windows Server 2008, Microsoft made their operating system 64 bit. This is done for several reasons, but the "main" part of it is that it supports more than 4 GB of memory. They've actually made it mandatory, so you cannot install it without less.

There are more to it, but mostly in memory allocations i.e. larger address spaces, wider registers and data paths. If a 64 bit operating system is handling a 64 bit compiled program or game, it will feel faster in that it got less limitations. This means that the processor can process more data at a time.

== Small Business Server 2008 ==

Microsoft have developed this branch of server operating systems to benefit smaller business that does not require big servers. By doing this, they've made a cheaper license that most business can afford with the ability to update.

=== Features and Components ===

*E-mail Server Application (Through Exchange).
*IIS Server Application. This is essentially a webserver.
*DHCP server
*DNS server
*Active Directory for handling Users and Groups
*Remote Web Workplace, Remote Desktop and VPN support
*Firewall
*Virus Scanner in the form of OneCare.

=== Limitations and Requirements ===

Windows Small Business Server 2008 got certain restrictions. This is because Microsoft wanted this to fit, as the name says, a small business so they put in some limitations to make the server operating system cheaper. Most business will not affected by these limitations. A lot of the limitations, like specific amount of space for emails, can be managed by implanting business policies - such as making sure you keep a tidy email account.

These limitations are:

*Only one SBS server in a domain. The domain can only handle more servers if these are of a different operating system, i.e. like linux, Windows Server etc.
*SBS is very picky about domains. It can only handle one and no child domains.
*Must be the root of the Active Directory forest.
*It is limited to 75 users (licenses).
*Earlier versions of SBS were limited to max 4 GB of memory. SBS 2008 requires a minimum of 4 GB and got a maximum limited of 32 GB. This is due to earlier versions being based on the x86 (32 bit) architecture while 2008 is based on x86-64 (64 bit). This change is because of Exchange Server 2007 is running in 64 bit.
*There are two different versions of SBS 2008. Standard Edition and Premium Edition. The difference between the two are: Premium includes a license to another Windows Server as well as MSSQL database.
*I am not certain if this limitation is still active in 2008 - but in Small Business Server 2003 service pack 2, the Exchange server limits you to 75 GB of emails.

If the business suddenly hits one of these limitations and needs to grow even further, it is possible to upgrade to a bigger license.

=== Installation of Small Server Business 2008 ===

Everybody knows how to press next and fill it out. So I will only fill this out with information that deems necessary to this project.

==== Partitioning ====

Normally, a server will have several harddrives in it and will run a certain kind of raid. Some people like to partition their harddrives to make it more "manageable" because they can assign certain drive letters to specific things, like documents for users etc. This is not at all necessary but can be easier to mange for certain people. I have decided not to do it - simply because it is not needed. By doing it this way, you will also force yourself to "read" drive/folder layouts and optimize them properly. This might be a linux thing but I prefer it this way.

In short, it's a matter of preference.

==== Updating and Virus Protection ====

Throughout the installation, it asks us whether or not we want to keep it up to date with updates and install it's virus scanner. We might as well, eh? Don't do it if you plan on using another one.

==== Post-installation ====

For the love of everything, remove UAC at once. It will make you hate everyone. Do that now.

=== Setting it Up ===

==== Internet Connectivity ====

An important part of a good business network, is having a constant connection to the Internet.

As we do not have a server with two ethernet interfaces, we are forced to do it a different way.

I believe that the best way to do it, is to let the router do the "sharing" and make the server give the IP, gateway and DNS information through it's DHCP server with a standard scope.

As I cannot do this with the current setup, I will not attempt it.

==== Adding Computers to the Domain ====

A pretty nice change in SBS is the ability to add computers. Not only does it add a computer, but it also installs certain tools to make sure that you can monitor a computer without having to physically look at it, i.e. it monitors virus scanner, status, updates etc and gives you a means to log on to it if needed. The way to do this is:

#Have a ready made XP installation. Login as Administrator.
#Go into a webbrowser and go to http://connect - or plug in a USB drive and tell the server to put the necessary files on there
#Follow the simple wizard.

==== Easy Configuration ====

Small Server Business 2008 has taken a hint from the unix world, have truly made it a lot easier to manage users and setting up the system. Upon installation, it starts up and installs the most commonly used services and utilities, such as DNS, IIS, Active Directory and more (These are also called roles and features). But the Windows SBS Console also allows for some amazing wizard options. If you want to add a user, it will automatically create a personal share for it, set the permissions for that folder as well as a "global" shared folder, create an email and send them a default "Welcome" email. Along with this, it can also print out this information. It is sort of a default way to do it, which can be very limiting to some.

While certainly streamlining the general process of managing and monitoring the server and the network, it can get very limiting in certain aspects and if you want to do something that isn't in the SBS Console, you will have to dig it out. If you are not familiar with earlier versions of SBS or Windows Server in general, you could get into a lot of problems doing something that was meant to be easy - like changing DHCP scope options, advanced permissions and logon scripts.

===== Shares =====

As stated above, the installation puts up a very standard, yet functional means of managing and taking care of shares. This is all very good but can be tedious to have to redo, since it just puts it in a standard folder called C:\Users\. If you have several partitions or harddrives, you'd most likely want to make use of them for user shares and documents. Thankfully, it is relatively easy to delete and redo the shares on different folders and is conveniently described in the SBS Console.

It is also with relative ease that you can make sure that it is only certain users who can enter certain directories/shares. It is done in the same way as most 2000+ Windows operating system - but I will just scratch it down quickly; You can do it the time consuming way or you can just add groups that certain people get into. This is all done through the standard Active Directory or can be done through the SBS Console.

I'd personally recommend keeping the sharing structure this way. There aren't many situations where you'd need to create it in a different way. So don't fix what isn't broken.

=== Tools of Small Server Business 2008 ===

Microsoft have expanded a bit on their tools from 2003, most notably Windows SBS Console and Server Manager.

There are 2 different version of Windows SBS Console, normal and advanced mode - though all that advanced does, is add a few extra features under "Tasks".

These two tools cannot really be compared as they are governing two different aspects of the server. While Windows SBS Console is more monitoring, adding of users, shares etc - which is more like every day stuff - the Server Manager is exactly what is said in the name. It manages the server and keeps logs of everything running in the background. Essentially, it is a glorified Event Log as well as a Add/Remove Windows Components - just a lot more advanced in it's features.

Through Server Manager, you can add, remove, start, stop, restart and configure most "roles". Microsoft now call the background things going, i.e. like DNS, DHCP servers "roles". Which makes sense. The things on the frontend of it all, is then called features. These features include tools of varying kind - i.e. for deeper management of every specific role. For example, there are the role called DNS Server and for it, there is a feature called DNS Server Tools. It also has the ability to add "role services" which is essentially a module that can be added to a specific role. An example is that File Services can have a role service called Windows Search Service.

As stated earlier, it is also a event viewer. It keeps track of just about everything that is going on and lists if there has been an error on a specific role or if something has gone horribly wrong - much like what the SBS Console does, except this is deeper - it will show a warning symbol or something else in the main panel and then you can start digging into it.

Obviously, you can find and configure more in details if you go directly to the role/service itself than if you went through SBS Console or Server Manager. Both of them, however, conveniently links to this. A thing to note, is that whatever you add through SBS Console will be added to Active Directory, i.e. users and groups added will be added in it. If you view through Active Directory, you will see these in it's own directory, so you can sort through what changes came from SBS Console.

I am really loving these extra tools, that just makes server monitoring, and to some extend, managing a server a lot easier. Just having a monitor attached to it with SBS Console running constantly will make sure that a lot of errors are caught early on.

== Network Diagram ==

This network diagram is suited for a very standard small business.

Note that since I do not have access to a computer with two ethernet interfaces, I have made it so I will not require this on the diagram. This can be a problem for certain businesses, since you cannot set up a proper firewall or monitor internet activity etc., except through a router's very limited monitoring tools and firewall. It is, however, possible.

[[Image:Sbs2008.png]]

It can be done in many ways, but this is a pretty good one for what we got.

Remember that this is not how it will look physically.

What we got is a router that connects to the internet. We could have connected the server directly to the router and the switch with it, but that could create a necessary burden on the router - which could strain the network if huge amounts of datas are passed through. You CAN do it but there is no reason to it, if you already got a switch handy. Why would it do this? Well, every packet going to the server would have to go into the inbuilt switch in the router as well as every packet aiming for the web, would have to go through it. Again, you can do it but it is not ideal.

Now that we cleared that up, we got a switch connected to the router. This switch is connected to the server and as many computers there are in the company. Notice that there easily could be more switches in the physical setup, due to computers being spread out in different departments and offices.

=== IP Table ===

{| border="1" class="wikitable"
|-
! IP
! Device
! DHCP or Static
! Gateway
! DNS
|-
| 192.168.1.1/24
| Router
| Static
|
|
|-
| 192.168.1.2/24
| SBS 2008 Server
| Static
|
|
|-
| 192.168.1.10-254/24
| Computers and Devices*
| DHCP
|
|
|}

<nowiki>
* Devices are network printers, IP phones and everything else that would require an IP.
</nowiki>

Pretty straightforward and easy.

=== How to Simulate at Mercantec ===

I do not have access to 15 computers or devices nor do I want to have to set up an entire Cisco Router just for this project, so I cut some corners on certain things but will still accomplish the same thing. I am only writing this here, so I can keep it organized and noted down.

<strike>After consulting Henrik about the network here, he suggested that I just use some IPs freely available here and create it out from that. These two are:</strike>

*<strike>192.168.138.128</strike>
*<strike>192.168.138.131</strike>

<strike>What I will do is give the server the first IP and the computer the second one. Because of this, I cannot install DHCP. I find that installing DHCP is pretty forward anyway and shouldn't need to be documented as we can just assume it is there. It is used for Internet Connectivity section and I will describe it like it is used like that. But if it is needed, let me know and I can find another way to do it.</strike>

After having tried the above, I've decided to just make a small network with just 2 computers in it with no connectivity to the internet. I enabled the scope, I described earlier and set it's gateway and DNS to the fictional router. I've updated both client and server so I shouldn't require any web access.

== Problems I Ran Into and How to Fix ==

I started out on a different network than I was going to end up on, so my DNS had already put in all of the information required for that IP and network. This made everything a bit tricky since my client wouldn't be able to resolve anything as the DNS server is out of reach.

To fix it, I had to reinstall the role DNS server and let it reconfigure itself. Afterwards, everything worked without a hitch.

Trillex small business server 2008

2009-09-23T10:34:20Z

Trillex:

= Deployment of Small Business Server 2008 =

THIS IS AN UNDERGOING PROJECT. MOST THINGS, IF NOT ALL, WILL CHANGE DURING THIS WEEK!

IF YOU SEE AN ERROR, CONTACT ME.

== Introduction ==

For this week, I am going to deploy a Small Business Server 2008, that would be suitable for a "standard" business.

Just to give me some kind of aim, I will put up these demands for myself:

The company got 15 computers. They require logins that goes through an exchange server. As any normal company, they also require emails, a website, personal login and a means of getting their files stored remotely on the server. A VPN connection for the workers as well as a means to manage the server remotely could also be mandatory.

=== Introduction to 64 bit Architecture ===

With Windows Server 2008, Microsoft made their operating system 64 bit. This is done for several reasons, but the "main" part of it is that it supports more than 4 GB of memory. They've actually made it mandatory, so you cannot install it without less.

There are more to it, but mostly in memory allocations i.e. larger address spaces, wider registers and data paths. If a 64 bit operating system is handling a 64 bit compiled program or game, it will feel faster in that it got less limitations. This means that the processor can process more data at a time.

== Small Business Server 2008 ==

Microsoft have developed this branch of server operating systems to benefit smaller business that does not require big servers. By doing this, they've made a cheaper license that most business can afford with the ability to update.

=== Features and Components ===

*E-mail Server Application (Through Exchange).
*IIS Server Application. This is essentially a webserver.
*DHCP server
*DNS server
*Active Directory for handling Users and Groups
*Remote Web Workplace, Remote Desktop and VPN support
*Firewall
*Virus Scanner in the form of OneCare.

=== Limitations and Requirements ===

Windows Small Business Server 2008 got certain restrictions. This is because Microsoft wanted this to fit, as the name says, a small business so they put in some limitations to make the server operating system cheaper. Most business will not affected by these limitations. A lot of the limitations, like specific amount of space for emails, can be managed by implanting business policies - such as making sure you keep a tidy email account.

These limitations are:

*Only one SBS server in a domain. The domain can only handle more servers if these are of a different operating system, i.e. like linux, Windows Server etc.
*SBS is very picky about domains. It can only handle one and no child domains.
*Must be the root of the Active Directory forest.
*It is limited to 75 users (licenses).
*Earlier versions of SBS were limited to max 4 GB of memory. SBS 2008 requires a minimum of 4 GB and got a maximum limited of 32 GB. This is due to earlier versions being based on the x86 (32 bit) architecture while 2008 is based on x86-64 (64 bit). This change is because of Exchange Server 2007 is running in 64 bit.
*There are two different versions of SBS 2008. Standard Edition and Premium Edition. The difference between the two are: Premium includes a license to another Windows Server as well as MSSQL database.
*I am not certain if this limitation is still active in 2008 - but in Small Business Server 2003 service pack 2, the Exchange server limits you to 75 GB of emails.

If the business suddenly hits one of these limitations and needs to grow even further, it is possible to upgrade to a bigger license.

=== Installation of Small Server Business 2008 ===

Everybody knows how to press next and fill it out. So I will only fill this out with information that deems necessary to this project.

==== Partitioning ====

Normally, a server will have several harddrives in it and will run a certain kind of raid. Some people like to partition their harddrives to make it more "manageable" because they can assign certain drive letters to specific things, like documents for users etc. This is not at all necessary but can be easier to mange for certain people. I have decided not to do it - simply because it is not needed. By doing it this way, you will also force yourself to "read" drive/folder layouts and optimize them properly. This might be a linux thing but I prefer it this way.

In short, it's a matter of preference.

==== Updating and Virus Protection ====

Throughout the installation, it asks us whether or not we want to keep it up to date with updates and install it's virus scanner. We might as well, eh? Don't do it if you plan on using another one.

==== Post-installation ====

For the love of everything, remove UAC at once. It will make you hate everyone. Do that now.

=== Setting it Up ===

==== Internet Connectivity ====

An important part of a good business network, is having a constant connection to the Internet.

As we do not have a server with two ethernet interfaces, we are forced to do it a different way.

I believe that the best way to do it, is to let the router do the "sharing" and make the server give the IP, gateway and DNS information through it's DHCP server with a standard scope.

As I cannot do this with the current setup, I will not attempt it.

==== Adding Computers to the Domain ====

A pretty nice change in SBS is the ability to add computers. Not only does it add a computer, but it also installs certain tools to make sure that you can monitor a computer without having to physically look at it, i.e. it monitors virus scanner, status, updates etc and gives you a means to log on to it if needed. The way to do this is:

#Have a ready made XP installation. Login as Administrator.
#Go into a webbrowser and go to http://connect - or plug in a USB drive and tell the server to put the necessary files on there
#Follow the simple wizard.

==== Easy Configuration ====

Small Server Business 2008 has taken a hint from the unix world, have truly made it a lot easier to manage users and setting up the system. Upon installation, it starts up and installs the most commonly used services and utilities, such as DNS, IIS, Active Directory and more (These are also called roles and features). But the Windows SBS Console also allows for some amazing wizard options. If you want to add a user, it will automatically create a personal share for it, set the permissions for that folder as well as a "global" shared folder, create an email and send them a default "Welcome" email. Along with this, it can also print out this information. It is sort of a default way to do it, which can be very limiting to some.

While certainly streamlining the general process of managing and monitoring the server and the network, it can get very limiting in certain aspects and if you want to do something that isn't in the SBS Console, you will have to dig it out. If you are not familiar with earlier versions of SBS or Windows Server in general, you could get into a lot of problems doing something that was meant to be easy - like changing DHCP scope options, advanced permissions and logon scripts.

===== Shares =====

As stated above, the installation puts up a very standard, yet functional means of managing and taking care of shares. This is all very good but can be tedious to have to redo, since it just puts it in a standard folder called C:\Users\. If you have several partitions or harddrives, you'd most likely want to make use of them for user shares and documents. Thankfully, it is relatively easy to delete and redo the shares on different folders and is conveniently described in the SBS Console.

It is also with relative ease that you can make sure that it is only certain users who can enter certain directories/shares. It is done in the same way as most 2000+ Windows operating system - but I will just scratch it down quickly; You can do it the time consuming way or you can just add groups that certain people get into. This is all done through the standard Active Directory or can be done through the SBS Console.

I'd personally recommend keeping the sharing structure this way. There aren't many situations where you'd need to create it in a different way. So don't fix what isn't broken.

=== Tools of Small Server Business 2008 ===

Microsoft have expanded a bit on their tools from 2003, most notably Windows SBS Console and Server Manager.

There are 2 different version of Windows SBS Console, normal and advanced mode - though all that advanced does, is add a few extra features under "Tasks".

These two tools cannot really be compared as they are governing two different aspects of the server. While Windows SBS Console is more monitoring, adding of users, shares etc - which is more like every day stuff - the Server Manager is exactly what is said in the name. It manages the server. It

== Network Diagram ==

This network diagram is suited for a very standard small business.

Note that since I do not have access to a computer with two ethernet interfaces, I have made it so I will not require this on the diagram. This can be a problem for certain businesses, since you cannot set up a proper firewall or monitor internet activity etc., except through a router's very limited monitoring tools and firewall. It is, however, possible.

[[Image:Sbs2008.png]]

It can be done in many ways, but this is a pretty good one for what we got.

Remember that this is not how it will look physically.

What we got is a router that connects to the internet. We could have connected the server directly to the router and the switch with it, but that could create a necessary burden on the router - which could strain the network if huge amounts of datas are passed through. You CAN do it but there is no reason to it, if you already got a switch handy. Why would it do this? Well, every packet going to the server would have to go into the inbuilt switch in the router as well as every packet aiming for the web, would have to go through it. Again, you can do it but it is not ideal.

Now that we cleared that up, we got a switch connected to the router. This switch is connected to the server and as many computers there are in the company. Notice that there easily could be more switches in the physical setup, due to computers being spread out in different departments and offices.

=== IP Table ===

{| border="1" class="wikitable"
|-
! IP
! Device
! DHCP or Static
! Gateway
! DNS
|-
| 192.168.1.1/24
| Router
| Static
|
|
|-
| 192.168.1.2/24
| SBS 2008 Server
| Static
|
|
|-
| 192.168.1.10-254/24
| Computers and Devices*
| DHCP
|
|
|}

<nowiki>
* Devices are network printers, IP phones and everything else that would require an IP.
</nowiki>

Pretty straightforward and easy.

=== How to Simulate at Mercantec ===

I do not have access to 15 computers or devices nor do I want to have to set up an entire Cisco Router just for this project, so I cut some corners on certain things but will still accomplish the same thing. I am only writing this here, so I can keep it organized and noted down.

<strike>After consulting Henrik about the network here, he suggested that I just use some IPs freely available here and create it out from that. These two are:</strike>

*<strike>192.168.138.128</strike>
*<strike>192.168.138.131</strike>

<strike>What I will do is give the server the first IP and the computer the second one. Because of this, I cannot install DHCP. I find that installing DHCP is pretty forward anyway and shouldn't need to be documented as we can just assume it is there. It is used for Internet Connectivity section and I will describe it like it is used like that. But if it is needed, let me know and I can find another way to do it.</strike>

After having tried the above, I've decided to just make a small network with just 2 computers in it with no connectivity to the internet. I enabled the scope, I described earlier and set it's gateway and DNS to the fictional router. I've updated both client and server so I shouldn't require any web access.

== Problems I Ran Into and How to Fix ==

I started out on a different network than I was going to end up on, so my DNS had already put in all of the information required for that IP and network. This made everything a bit tricky since my client wouldn't be able to resolve anything as the DNS server is out of reach.

To fix it, I had to reinstall the role DNS server and let it reconfigure itself. Afterwards, everything worked without a hitch.

Trillex small business server 2008

2009-09-23T10:24:20Z

Trillex: /* Easy Configuration */

= Deployment of Small Business Server 2008 =

THIS IS AN UNDERGOING PROJECT. MOST THINGS, IF NOT ALL, WILL CHANGE DURING THIS WEEK!

IF YOU SEE AN ERROR, CONTACT ME.

== Introduction ==

For this week, I am going to deploy a Small Business Server 2008, that would be suitable for a "standard" business.

Just to give me some kind of aim, I will put up these demands for myself:

The company got 15 computers. They require logins that goes through an exchange server. As any normal company, they also require emails, a website, personal login and a means of getting their files stored remotely on the server. A VPN connection for the workers as well as a means to manage the server remotely could also be mandatory.

=== Introduction to 64 bit Architecture ===

With Windows Server 2008, Microsoft made their operating system 64 bit. This is done for several reasons, but the "main" part of it is that it supports more than 4 GB of memory. They've actually made it mandatory, so you cannot install it without less.

There are more to it, but mostly in memory allocations i.e. larger address spaces, wider registers and data paths. If a 64 bit operating system is handling a 64 bit compiled program or game, it will feel faster in that it got less limitations. This means that the processor can process more data at a time.

== Small Business Server 2008 ==

Microsoft have developed this branch of server operating systems to benefit smaller business that does not require big servers. By doing this, they've made a cheaper license that most business can afford with the ability to update.

=== Features and Components ===

*E-mail Server Application (Through Exchange).
*IIS Server Application. This is essentially a webserver.
*DHCP server
*DNS server
*Active Directory for handling Users and Groups
*Remote Web Workplace, Remote Desktop and VPN support
*Firewall
*Virus Scanner in the form of OneCare.

=== Limitations and Requirements ===

Windows Small Business Server 2008 got certain restrictions. This is because Microsoft wanted this to fit, as the name says, a small business so they put in some limitations to make the server operating system cheaper. Most business will not affected by these limitations. A lot of the limitations, like specific amount of space for emails, can be managed by implanting business policies - such as making sure you keep a tidy email account.

These limitations are:

*Only one SBS server in a domain. The domain can only handle more servers if these are of a different operating system, i.e. like linux, Windows Server etc.
*SBS is very picky about domains. It can only handle one and no child domains.
*Must be the root of the Active Directory forest.
*It is limited to 75 users (licenses).
*Earlier versions of SBS were limited to max 4 GB of memory. SBS 2008 requires a minimum of 4 GB and got a maximum limited of 32 GB. This is due to earlier versions being based on the x86 (32 bit) architecture while 2008 is based on x86-64 (64 bit). This change is because of Exchange Server 2007 is running in 64 bit.
*There are two different versions of SBS 2008. Standard Edition and Premium Edition. The difference between the two are: Premium includes a license to another Windows Server as well as MSSQL database.
*I am not certain if this limitation is still active in 2008 - but in Small Business Server 2003 service pack 2, the Exchange server limits you to 75 GB of emails.

If the business suddenly hits one of these limitations and needs to grow even further, it is possible to upgrade to a bigger license.

=== Installation of Small Server Business 2008 ===

Everybody knows how to press next and fill it out. So I will only fill this out with information that deems necessary to this project.

==== Partitioning ====

Normally, a server will have several harddrives in it and will run a certain kind of raid. Some people like to partition their harddrives to make it more "manageable" because they can assign certain drive letters to specific things, like documents for users etc. This is not at all necessary but can be easier to mange for certain people. I have decided not to do it - simply because it is not needed. By doing it this way, you will also force yourself to "read" drive/folder layouts and optimize them properly. This might be a linux thing but I prefer it this way.

In short, it's a matter of preference.

==== Updating and Virus Protection ====

Throughout the installation, it asks us whether or not we want to keep it up to date with updates and install it's virus scanner. We might as well, eh? Don't do it if you plan on using another one.

==== Post-installation ====

For the love of everything, remove UAC at once. It will make you hate everyone. Do that now.

=== Setting it Up ===

==== Internet Connectivity ====

An important part of a good business network, is having a constant connection to the Internet.

As we do not have a server with two ethernet interfaces, we are forced to do it a different way.

I believe that the best way to do it, is to let the router do the "sharing" and make the server give the IP, gateway and DNS information through it's DHCP server with a standard scope.

As I cannot do this with the current setup, I will not attempt it.

==== Adding Computers to the Domain ====

A pretty nice change in SBS is the ability to add computers. Not only does it add a computer, but it also installs certain tools to make sure that you can monitor a computer without having to physically look at it, i.e. it monitors virus scanner, status, updates etc and gives you a means to log on to it if needed. The way to do this is:

#Have a ready made XP installation. Login as Administrator.
#Go into a webbrowser and go to http://connect - or plug in a USB drive and tell the server to put the necessary files on there
#Follow the simple wizard.

==== Easy Configuration ====

Small Server Business 2008 has taken a hint from the unix world, have truly made it a lot easier to manage users and setting up the system. Upon installation, it starts up and installs the most commonly used services and utilities, such as DNS, IIS, Active Directory and more (These are also called roles and features). But the Windows SBS Console also allows for some amazing wizard options. If you want to add a user, it will automatically create a personal share for it, set the permissions for that folder as well as a "global" shared folder, create an email and send them a default "Welcome" email. Along with this, it can also print out this information. It is sort of a default way to do it, which can be very limiting to some.

While certainly streamlining the general process of managing and monitoring the server and the network, it can get very limiting in certain aspects and if you want to do something that isn't in the SBS Console, you will have to dig it out. If you are not familiar with earlier versions of SBS or Windows Server in general, you could get into a lot of problems doing something that was meant to be easy - like changing DHCP scope options, advanced permissions and logon scripts.

===== Shares =====

As stated above, the installation puts up a very standard, yet functional means of managing and taking care of shares. This is all very good but can be tedious to have to redo, since it just puts it in a standard folder called C:\Users\. If you have several partitions or harddrives, you'd most likely want to make use of them for user shares and documents. Thankfully, it is relatively easy to delete and redo the shares on different folders and is conveniently described in the SBS Console.

It is also with relative ease that you can make sure that it is only certain users who can enter certain directories/shares. It is done in the same way as most 2000+ Windows operating system - but I will just scratch it down quickly; You can do it the time consuming way or you can just add groups that certain people get into. This is all done through the standard Active Directory or can be done through the SBS Console.

I'd personally recommend keeping the sharing structure this way. There aren't many situations where you'd need to create it in a different way. So don't fix what isn't broken.

== Network Diagram ==

This network diagram is suited for a very standard small business.

Note that since I do not have access to a computer with two ethernet interfaces, I have made it so I will not require this on the diagram. This can be a problem for certain businesses, since you cannot set up a proper firewall or monitor internet activity etc., except through a router's very limited monitoring tools and firewall. It is, however, possible.

[[Image:Sbs2008.png]]

It can be done in many ways, but this is a pretty good one for what we got.

Remember that this is not how it will look physically.

What we got is a router that connects to the internet. We could have connected the server directly to the router and the switch with it, but that could create a necessary burden on the router - which could strain the network if huge amounts of datas are passed through. You CAN do it but there is no reason to it, if you already got a switch handy. Why would it do this? Well, every packet going to the server would have to go into the inbuilt switch in the router as well as every packet aiming for the web, would have to go through it. Again, you can do it but it is not ideal.

Now that we cleared that up, we got a switch connected to the router. This switch is connected to the server and as many computers there are in the company. Notice that there easily could be more switches in the physical setup, due to computers being spread out in different departments and offices.

=== IP Table ===

{| border="1" class="wikitable"
|-
! IP
! Device
! DHCP or Static
! Gateway
! DNS
|-
| 192.168.1.1/24
| Router
| Static
|
|
|-
| 192.168.1.2/24
| SBS 2008 Server
| Static
|
|
|-
| 192.168.1.10-254/24
| Computers and Devices*
| DHCP
|
|
|}

<nowiki>
* Devices are network printers, IP phones and everything else that would require an IP.
</nowiki>

Pretty straightforward and easy.

=== How to Simulate at Mercantec ===

I do not have access to 15 computers or devices nor do I want to have to set up an entire Cisco Router just for this project, so I cut some corners on certain things but will still accomplish the same thing. I am only writing this here, so I can keep it organized and noted down.

<strike>After consulting Henrik about the network here, he suggested that I just use some IPs freely available here and create it out from that. These two are:</strike>

*<strike>192.168.138.128</strike>
*<strike>192.168.138.131</strike>

<strike>What I will do is give the server the first IP and the computer the second one. Because of this, I cannot install DHCP. I find that installing DHCP is pretty forward anyway and shouldn't need to be documented as we can just assume it is there. It is used for Internet Connectivity section and I will describe it like it is used like that. But if it is needed, let me know and I can find another way to do it.</strike>

After having tried the above, I've decided to just make a small network with just 2 computers in it with no connectivity to the internet. I enabled the scope, I described earlier and set it's gateway and DNS to the fictional router. I've updated both client and server so I shouldn't require any web access.

== Problems I Ran Into and How to Fix ==

I started out on a different network than I was going to end up on, so my DNS had already put in all of the information required for that IP and network. This made everything a bit tricky since my client wouldn't be able to resolve anything as the DNS server is out of reach.

To fix it, I had to reinstall the role DNS server and let it reconfigure itself. Afterwards, everything worked without a hitch.

Trillex small business server 2008

2009-09-23T10:10:04Z

Trillex:

Trillex small business server 2008

2009-09-23T10:07:34Z

Trillex:

Trillex small business server 2008

2009-09-23T09:11:12Z

Trillex:

Trillex - programming in perl with cgi and dbi

2009-09-23T06:51:08Z

Trillex:

[[Category:Linux]][[Category:Perl]][[Category:Projekt]]
= Programming: Perl with Webinterface and Database Injections =
== Introduction ==
As a final project in Perl, I decided to make a script that could be useful as a linux adminstrator. The script is very situational, however, since it makes use of a specific setup.

The idea of the script can be changed and used for many situation, especially when you just need to inject simple things into a table. It certainly beats having to do it manually through that cursed client or through other means like phpmyadmin etc.

What the script does, is add a new user to the database "pureftpd" in the table "ftpd". This is in a MySQL database. The only situation you'd need to do this, is when you have set your FTP daemon up for virtual users, i.e. the user accessing the FTP does not have access to the server itself through SSH, like it would normally if we create another user on most UNIX systems.

== The Script ==
<source lang=perl>
#!/usr/bin/perl
use strict;
use warnings;
use CGI;
use DBI;
use CGI::Carp qw(fatalsToBrowser);

print CGI::header();

my $username = dbquote(CGI::param('user'));
my $status = dbquote(CGI::param('status'));
my $password = dbquote(CGI::param('password'));
my $uid = dbquote(CGI::param('uid'));
my $gid = dbquote(CGI::param('gid'));
my $dir = dbquote(CGI::param('dir'));
my $upload = dbquote(CGI::param('upload'));
my $download = dbquote(CGI::param('download'));
my $comment = dbquote(CGI::param('comment'));
my $ipaccess = dbquote(CGI::param('ipaccess'));
my $quotasize = dbquote(CGI::param('quotasize'));
my $quotafiles = dbquote(CGI::param('quotafiles'));

unless($username) {
print <<PAGE;
<h1>Add a FTP account</h1>
<form action=testadddatabase.pl method=post>
Username: <input type=text name=user><br>
Status: <input type=text name=status><br>
Password: <input type=text name=password><br>
User ID: <input type=text name=uid><br>
Group ID: <input type=text name=gid><br>
Home Dir: <input type=text name=dir><br>
Upload Limit: <input type=text name=upload><br>
Download Limit: <input type=text name=download><br>
Comment: <input type=text name=comment><br>
IP Access: <input type=text name=ipaccess><br>
Quota Size: <input type=text name=quotasize><br>
Quota Files: <input type=text name=quotafiles><br>
<input type=submit value="Add an FTP account">
</form>
PAGE

exit;
}

my $dbh = DBI->connect("dbi:mysql:pureftpd:localhost", "user", "password");

my $sth = $dbh->prepare("insert into ftpd(User, status, Password, Uid, Gid, Dir, ULBandwidth, DLBandwidth, comment, ipaccess, QuotaSize, Quotafiles) values('$username', '$status', '$password', '$uid', '$gid', '$dir', '$upload', '$download', '$comment', '$ipaccess', '$quotasize', '$quotafiles')");

$sth->execute();

print <<PAGE;
<h1>Account added</h1>
The account $username was just added. want to <a href=testadddatabase.pl>add another</a>?
PAGE

sub dbquote {
my ($str) = @_;

$str =~ s/”/\\”/g;
$str =~ s/\\/\\\\/g;
$str =~ s/’/\\’/g;

return $str;
}
</source>

=== Breaking it Down ===

I won't use comments (#) since I will not be able to explain enough in it. I will, hopefully, explain everything here so a newbie can look at it and understand it.

<source lang=perl>
#!/usr/bin/perl
use strict;
use warnings;
use CGI;
use DBI;
use CGI::Carp qw(fatalsToBrowser);
</source>

Essentially this is the start of the script. It tells it what kind of "modules" to make use of. These modules can contain certain functions or be able to give you more information on errors etc.

<source lang=perl>
#!/usr/bin/perl
</source>

What this does is explain that this is now a perl script and it needs to be compiled at /usr/bin/perl. This is, obviously, different on Windows machines and can differ from linux distro.

<source lang=perl>
use strict;
</source>

Strict makes it a bit more "strict" and pretty much slaps you, if you are about to do something nasty in your script that could create a mess. An example is that without strict, you don't have to define variables first but can just write it out. This can cause issues with typos and such, which could lead to strange bugs that will be impossible, or very hard, to find. It's good for beginners.

<source lang=perl>
use warnings;
</source>

Does pretty much what it says. It gives you detailed information if it sees an error in your script when you run it, and outputs it to you. In some situations, it will even tell you exactly what is wrong. Always a good idea to use this, at least for debugging purposes.

<source lang=perl>
use CGI;
</source>

This loads a module for use in CGI, Common Gateway Interface. This is usually used when you want to make web development with perl. It's what making this script work

<source lang=perl>
use DBI;
</source>

Stands for DataBase Interface. Essentially it's the same thing as the CGI, except that it is for database use instead. This can connect, change, view, create databases of various kinds, like SQL, Oracle and more. A very powerful tool.

<source lang=perl>
use CGI::Carp qw(fatalsToBrowser);
</source>

You might have noticed that we have two calls for CGI. This one, however, only calls the functions for Carp with fatalsToBrowser. So to make sure that there is absolutely no chance of messing up, I included a call for normal CGI and then just this one.

<source lang=perl>
print CGI::header();
</source>

What this does, is to define the Content-type in the html code it is going to create through CGI. It essentially makes the script a webpage by defining this.

<source lang=perl>
my $username = dbquote(CGI::param('user'));
my $status = dbquote(CGI::param('status'));
my $password = dbquote(CGI::param('password'));
my $uid = dbquote(CGI::param('uid'));
my $gid = dbquote(CGI::param('gid'));
my $dir = dbquote(CGI::param('dir'));
my $upload = dbquote(CGI::param('upload'));
my $download = dbquote(CGI::param('download'));
my $comment = dbquote(CGI::param('comment'));
my $ipaccess = dbquote(CGI::param('ipaccess'));
my $quotasize = dbquote(CGI::param('quotasize'));
my $quotafiles = dbquote(CGI::param('quotafiles'));
</source>

What this does is define our variables. 'my' "creates" them and the dollar sign ($) defines that it's a variable that will only hold one value. In perl, it is called a scalar. The equal shows it what kind of variable it should be defined with. dbquote is a subroutine, which is explained later. CGI::param'value' will get filled out later on with a value of some kind, through the script. Notice that the "params", the parameters, all have different names. This is what is used in the HTML page. Make sure these add up.

<source lang=perl>
unless($username) {
print <<PAGE;
<h1>Add a FTP account</h1>
<form action=testadddatabase.pl method=post>
Username: <input type=text name=user><br>
Status: <input type=text name=status><br>
Password: <input type=text name=password><br>
User ID: <input type=text name=uid><br>
Group ID: <input type=text name=gid><br>
Home Dir: <input type=text name=dir><br>
Upload Limit: <input type=text name=upload><br>
Download Limit: <input type=text name=download><br>
Comment: <input type=text name=comment><br>
IP Access: <input type=text name=ipaccess><br>
Quota Size: <input type=text name=quotasize><br>
Quota Files: <input type=text name=quotafiles><br>
<input type=submit value="Add an FTP account">
</form>
PAGE

exit;
}
</source>

This creates a website inside the script you are running. This makes it so you don't have to have a HTML page that links to this form. It essentially makes a frontend to the script.

<source lang=perl>
unless($username) {
</source>

This checks what "value" is being passed about. If it already had some information (i.e. the form has already been used), it won't call forth the form. If there is nothing, it will. The "{" starts the "form script" itself.

<source lang=perl>
print <<PAGE;
<h1>Add a FTP account</h1>
<form action=testadddatabase.pl method=post>
Username: <input type=text name=user><br>
Status: <input type=text name=status><br>
Password: <input type=text name=password><br>
User ID: <input type=text name=uid><br>
Group ID: <input type=text name=gid><br>
Home Dir: <input type=text name=dir><br>
Upload Limit: <input type=text name=upload><br>
Download Limit: <input type=text name=download><br>
Comment: <input type=text name=comment><br>
IP Access: <input type=text name=ipaccess><br>
Quota Size: <input type=text name=quotasize><br>
Quota Files: <input type=text name=quotafiles><br>
<input type=submit value="Add an FTP account">
</form>
PAGE

exit;
}
</source>

This creates a webpage inside the script. As you can see, it is just basic HTML code, which points to the script itself so it can run what input the form gives us. Notice that the "name=" refers to something I showed earlier. Exit stops it.

<source lang=perl>
my $dbh = DBI->connect("dbi:mysql:pureftpd:localhost", "user", "password");
</source>

This defines the variable $dbh. It calls the connect function from DBI module. Then makes use of the input in the parenthesis. It goes like this: "DBI:what kind of database:the database's name:host where the database is". User and password is self explanatory.

<source lang=perl>
my $sth = $dbh->prepare("insert into ftpd(User, status, Password, Uid, Gid, Dir, ULBandwidth, DLBandwidth, comment, ipaccess, QuotaSize, Quotafiles) values('$username', '$status', '$password', '$uid', '$gid', '$dir', '$upload', '$download', '$comment', '$ipaccess', '$quotasize', '$quotafiles')");

$sth->execute();
</source>

Defines the variable $sth and then calls $dbh with the added function prepare. This inserts the values from the various variables defined earlier in the script. It inserts it into the table "ftpd".

It then executes all of it. Doing it this way, gives it a better, more readable output to put into the database.

<source lang=perl>
print <<PAGE;
<h1>Account added</h1>
The account $username was just added. want to <a href=testadddatabase.pl>add another</a>?
PAGE
</source>

When the previous have been executed, this creates another website that links to the original script if you want to create another user account.

<source lang=perl>
sub dbquote {
my ($str) = @_;

$str =~ s/”/\\”/g;
$str =~ s/\\/\\\\/g;
$str =~ s/’/\\’/g;

return $str;
}
</source>

This creates a subroutine to a function encountered earlier. What it does, is make sure that there won't be any syntax errors through a simple method of regular expressions (regex). If this wasn't added and someone put in an odd symbol, like " \ / or ', it could wreck the script and add odd things to the database. With this, it adds another \, indicating that this is still a text and not an essential command.

= Conclusion =

This is a basic script but is very powerful, because it simplifies an action that could have taken several minutes. Now it just takes seconds. Imagine what you could do with more advanced scripts.

Trillex small business server 2008

2009-09-23T06:26:37Z

Trillex:

Trillex small business server 2008

2009-09-23T06:23:54Z

Trillex:

Trillex small business server 2008

2009-09-22T12:10:43Z

Trillex:

Trillex - programming in perl with cgi and dbi

2009-09-22T11:53:32Z

Trillex:

[[Category:Linux]][[Category:Perl]][[Category:Projekt]]
= Programming: Perl with Webinterface and Database Injections =
== Introduction ==
As a final project in Perl, I decided to make a script that could be useful as a linux adminstrator. The script is very situational, however, since it makes use of a specific setup.

The idea of the script can be changed and used for many situation, especially when you just need to inject simple things into a table. It certainly beats having to do it manually through that cursed client or through other means like phpmyadmin etc.

What the script does, is add a new user to the database "pureftpd" in the table "ftpd". This is in a MySQL database. The only situation you'd need to do this, is when you have set your FTP daemon up for virtual users, i.e. the user accessing the FTP does not have access to the server itself through SSH, like it would normally if we create another user on most UNIX systems.

== The Script ==
<source lang=perl>
#!/usr/bin/perl
use strict;
use warnings;
use CGI;
use DBI;
use CGI::Carp qw(fatalsToBrowser);

print CGI::header();

my $username = dbquote(CGI::param('user'));
my $status = dbquote(CGI::param('status'));
my $password = dbquote(CGI::param('password'));
my $uid = dbquote(CGI::param('uid'));
my $gid = dbquote(CGI::param('gid'));
my $dir = dbquote(CGI::param('dir'));
my $upload = dbquote(CGI::param('upload'));
my $download = dbquote(CGI::param('download'));
my $comment = dbquote(CGI::param('comment'));
my $ipaccess = dbquote(CGI::param('ipaccess'));
my $quotasize = dbquote(CGI::param('quotasize'));
my $quotafiles = dbquote(CGI::param('quotafiles'));

unless($username) {
print <<PAGE;
<h1>Add a FTP account</h1>
<form action=testadddatabase.pl method=post>
Username: <input type=text name=user><br>
Status: <input type=text name=status><br>
Password: <input type=text name=password><br>
User ID: <input type=text name=uid><br>
Group ID: <input type=text name=gid><br>
Home Dir: <input type=text name=dir><br>
Upload Limit: <input type=text name=upload><br>
Download Limit: <input type=text name=download><br>
Comment: <input type=text name=comment><br>
IP Access: <input type=text name=ipaccess><br>
Quota Size: <input type=text name=quotasize><br>
Quota Files: <input type=text name=quotafiles><br>
<input type=submit value="Add an FTP account">
</form>
PAGE

exit;
}

my $dbh = DBI->connect("dbi:mysql:pureftpd:localhost", "user", "password");

my $sth = $dbh->prepare("insert into ftpd(User, status, Password, Uid, Gid, Dir, ULBandwidth, DLBandwidth, comment, ipaccess, QuotaSize, Quotafiles) values('$username', '$status', '$password', '$uid', '$gid', '$dir', '$upload', '$download', '$comment', '$ipaccess', '$quotasize', '$quotafiles')");

$sth->execute();

print <<PAGE;
<h1>Account added</h1>
The account $username was just added. want to <a href=testadddatabase.pl>add another</a>?
PAGE

sub dbquote {
my ($str) = @_;

$str =~ s/”/\\”/g;
$str =~ s/\\/\\\\/g;
$str =~ s/’/\\’/g;

return $str;
}
</source>

=== Breaking it Down ===

I won't use comments (#) since I will not be able to explain enough in it. I will, hopefully, explain everything here so a newbie can look at it and understand it.

<source lang=perl>
#!/usr/bin/perl
use strict;
use warnings;
use CGI;
use DBI;
use CGI::Carp qw(fatalsToBrowser);
</source>

Essentially this is the start of the script. It tells it what kind of "modules" to make use of. These modules can contain certain functions or be able to give you more information on errors etc.

<source lang=perl>
#!/usr/bin/perl
</source>

What this does is explain that this is now a perl script and it needs to be compiled at /usr/bin/perl. This is, obviously, different on Windows machines and can differ from linux distro.

<source lang=perl>
use strict;
</source>

Strict makes it a bit more "strict" and pretty much slaps you, if you are about to do something nasty in your script that could create a mess. An example is that without strict, you don't have to define variables first but can just write it out. This can cause issues with typos and such, which could lead to strange bugs that will be impossible, or very hard, to find. It's good for beginners.

<source lang=perl>
use warnings;
</source>

Does pretty much what it says. It gives you detailed information if it sees an error in your script when you run it, and outputs it to you. In some situations, it will even tell you exactly what is wrong. Always a good idea to use this, at least for debugging purposes.

<source lang=perl>
use CGI;
</source>

This loads a module for use in CGI, Common Gateway Interface. This is usually used when you want to make web development with perl. It's what making this script work

<source lang=perl>
use DBI;
</source>

Stands for DataBase Interface. Essentially it's the same thing as the CGI, except that it is for database use instead. This can connect, change, view, create databases of various kinds, like SQL, Oracle and more. A very powerful tool.

<source lang=perl>
use CGI::Carp qw(fatalsToBrowser);
</source>

You might have noticed that we have two calls for CGI. This one, however, only calls the functions for Carp with fatalsToBrowser. So to make sure that there is absolutely no chance of messing up, I included a call for normal CGI and then just this one.

<source lang=perl>
print CGI::header();
</source>

What this does, is to define the Content-type in the html code it is going to create through CGI. It essentially makes the script a webpage by defining this.

<source lang=perl>
my $username = dbquote(CGI::param('user'));
my $status = dbquote(CGI::param('status'));
my $password = dbquote(CGI::param('password'));
my $uid = dbquote(CGI::param('uid'));
my $gid = dbquote(CGI::param('gid'));
my $dir = dbquote(CGI::param('dir'));
my $upload = dbquote(CGI::param('upload'));
my $download = dbquote(CGI::param('download'));
my $comment = dbquote(CGI::param('comment'));
my $ipaccess = dbquote(CGI::param('ipaccess'));
my $quotasize = dbquote(CGI::param('quotasize'));
my $quotafiles = dbquote(CGI::param('quotafiles'));
</source>

What this does is define our variables. 'my' "creates" them and the dollar sign ($) defines that it's a variable that will only hold one value. In perl, it is called a scalar. The equal shows it what kind of variable it should be defined with. dbquote fetches a value, which it does inside it's parentheses. CGI::param'value' will get filled out later on with a value of some kind, through the script. Notice that the "params", the parameters, all have different names. This is what is used in the HTML page. Make sure these add up.

<source lang=perl>
unless($username) {
print <<PAGE;
<h1>Add a FTP account</h1>
<form action=testadddatabase.pl method=post>
Username: <input type=text name=user><br>
Status: <input type=text name=status><br>
Password: <input type=text name=password><br>
User ID: <input type=text name=uid><br>
Group ID: <input type=text name=gid><br>
Home Dir: <input type=text name=dir><br>
Upload Limit: <input type=text name=upload><br>
Download Limit: <input type=text name=download><br>
Comment: <input type=text name=comment><br>
IP Access: <input type=text name=ipaccess><br>
Quota Size: <input type=text name=quotasize><br>
Quota Files: <input type=text name=quotafiles><br>
<input type=submit value="Add an FTP account">
</form>
PAGE

exit;
}
</source>

This creates a website inside the script you are running. This makes it so you don't have to have a HTML page that links to this form. It essentially makes a frontend to the script.

<source lang=perl>
unless($username) {
</source>

This checks what "value" is being passed about. If it already had some information (i.e. the form has already been used), it won't call forth the form. If there is nothing, it will. The "{" starts the "form script" itself.

<source lang=perl>
print <<PAGE;
<h1>Add a FTP account</h1>
<form action=testadddatabase.pl method=post>
Username: <input type=text name=user><br>
Status: <input type=text name=status><br>
Password: <input type=text name=password><br>
User ID: <input type=text name=uid><br>
Group ID: <input type=text name=gid><br>
Home Dir: <input type=text name=dir><br>
Upload Limit: <input type=text name=upload><br>
Download Limit: <input type=text name=download><br>
Comment: <input type=text name=comment><br>
IP Access: <input type=text name=ipaccess><br>
Quota Size: <input type=text name=quotasize><br>
Quota Files: <input type=text name=quotafiles><br>
<input type=submit value="Add an FTP account">
</form>
PAGE

exit;
}
</source>

This creates a webpage inside the script. As you can see, it is just basic HTML code, which points to the script itself so it can run what input the form gives us. Notice that the "name=" refers to something I showed earlier. Exit stops it.

<source lang=perl>

print <<PAGE;
<h1>Account added</h1>
The account $username was just added. want to <a href=testadddatabase.pl>add another</a>?
PAGE

sub dbquote {
my ($str) = @_;

$str =~ s/”/\\”/g;
$str =~ s/\\/\\\\/g;
$str =~ s/’/\\’/g;

return $str;
}
</source>

<source lang=perl>
my $dbh = DBI->connect("dbi:mysql:pureftpd:localhost", "user", "password");
</source>

This defines the variable $dbh. It calls the connect function from DBI module. Then makes use of the input in the parenthesis. It goes like this: "DBI:what kind of database:the database's name:host where the database is". User and password is self explanatory.

<source lang=perl>
my $sth = $dbh->prepare("insert into ftpd(User, status, Password, Uid, Gid, Dir, ULBandwidth, DLBandwidth, comment, ipaccess, QuotaSize, Quotafiles) values('$username', '$status', '$password', '$uid', '$gid', '$dir', '$upload', '$download', '$comment', '$ipaccess', '$quotasize', '$quotafiles')");

$sth->execute();
</source>

Defines the variable $sth and then calls $dbh with the added function prepare. This inserts the values from the various variables defined earlier in the script. It inserts it into the table "ftpd".

It then executes all of it. Doing this kind of gives it a better, more readable output to put into the database.

Trillex small business server 2008

2009-09-22T10:24:56Z

Trillex:

Trillex small business server 2008

2009-09-22T10:11:18Z

Trillex:

Trillex small business server 2008

2009-09-22T08:51:50Z

Trillex:

Trillex small business server 2008

2009-09-22T08:45:20Z

Trillex:

Trillex small business server 2008

2009-09-22T08:40:03Z

Trillex:

Trillex small business server 2008

2009-09-22T08:25:28Z

Trillex:

Trillex small business server 2008

2009-09-22T08:14:09Z

Trillex:

Trillex small business server 2008

2009-09-22T07:52:17Z

Trillex:

Trillex small business server 2008

2009-09-22T07:25:52Z

Trillex:

Trillex small business server 2008

2009-09-22T07:09:30Z

Trillex:

Trillex small business server 2008

2009-09-22T07:01:58Z

Trillex:

Trillex small business server 2008

2009-09-22T07:01:32Z

Trillex:

Trillex small business server 2008

2009-09-22T06:59:37Z

Trillex:

Trillex small business server 2008

2009-09-22T06:56:36Z

Trillex:

Trillex small business server 2008

2009-09-22T06:55:51Z

Trillex:

Trillex small business server 2008

2009-09-22T06:53:10Z

Trillex:

Trillex small business server 2008

2009-09-22T06:29:20Z

Trillex:

Trillex - programming in perl with cgi and dbi

2009-09-22T06:26:09Z

Trillex:

[[Category:Linux]][[Category:Perl]][[Category:Projekt]]
= Programming: Perl with Webinterface and Database Injections =
== Introduction ==
As a final project in Perl, I decided to make a script that could be useful as a linux adminstrator. The script is very situational, however, since it makes use of a specific setup.

The idea of the script can be changed and used for many situation, especially when you just need to inject simple things into a table. It certainly beats having to do it manually through that cursed client or through other means like phpmyadmin etc.

What the script does, is add a new user to the database "pureftpd" in the table "ftpd". This is in a MySQL database. The only situation you'd need to do this, is when you have set your FTP daemon up for virtual users, i.e. the user accessing the FTP does not have access to the server itself through SSH, like it would normally if we create another user on most UNIX systems.

== The Script ==
<source lang=perl>
#!/usr/bin/perl
use strict;
use warnings;
use CGI;
use DBI;
use CGI::Carp qw(fatalsToBrowser);

print CGI::header();

my $username = dbquote(CGI::param('user'));
my $status = dbquote(CGI::param('status'));
my $password = dbquote(CGI::param('password'));
my $uid = dbquote(CGI::param('uid'));
my $gid = dbquote(CGI::param('gid'));
my $dir = dbquote(CGI::param('dir'));
my $upload = dbquote(CGI::param('upload'));
my $download = dbquote(CGI::param('download'));
my $comment = dbquote(CGI::param('comment'));
my $ipaccess = dbquote(CGI::param('ipaccess'));
my $quotasize = dbquote(CGI::param('quotasize'));
my $quotafiles = dbquote(CGI::param('quotafiles'));

unless($username) {
print <<PAGE;
<h1>Add a FTP account</h1>
<form action=testadddatabase.pl method=post>
Username: <input type=text name=user><br>
Status: <input type=text name=status><br>
Password: <input type=text name=password><br>
User ID: <input type=text name=uid><br>
Group ID: <input type=text name=gid><br>
Home Dir: <input type=text name=dir><br>
Upload Limit: <input type=text name=upload><br>
Download Limit: <input type=text name=download><br>
Comment: <input type=text name=comment><br>
IP Access: <input type=text name=ipaccess><br>
Quota Size: <input type=text name=quotasize><br>
Quota Files: <input type=text name=quotafiles><br>
<input type=submit value="Add an FTP account">
</form>
PAGE

exit;
}

my $dbh = DBI->connect("dbi:mysql:pureftpd:localhost", "user", "password");

my $sth = $dbh->prepare("insert into ftpd(User, status, Password, Uid, Gid, Dir, ULBandwidth, DLBandwidth, comment, ipaccess, QuotaSize, Quotafiles) values('$username', '$status', '$password', '$uid', '$gid', '$dir', '$upload', '$download', '$comment', '$ipaccess', '$quotasize', '$quotafiles')");
ye
$sth->execute();

print <<PAGE;
<h1>Account added</h1>
The account $username was just added. want to <a href=testadddatabase.pl>add another</a>?
PAGE

sub dbquote {
my ($str) = @_;

$str =~ s/”/\\”/g;
$str =~ s/\\/\\\\/g;
$str =~ s/’/\\’/g;

return $str;
}
</source>

=== Breaking it Down ===

I won't use comments (#) since I will not be able to explain enough in it. I will, hopefully, explain everything here so a newbie can look at it and understand it.

<source lang=perl>
#!/usr/bin/perl
use strict;
use warnings;
use CGI;
use DBI;
use CGI::Carp qw(fatalsToBrowser);
</source>

Essentially this is the start of the script. It tells it what kind of "modules" to make use of. These modules can contain certain functions or be able to give you more information on errors etc.

<source lang=perl>
#!/usr/bin/perl
</source>

What this does is explain that this is now a perl script and it needs to be compiled at /usr/bin/perl. This is, obviously, different on Windows machines and can differ from linux distro.

<source lang=perl>
use strict;
</source>

Strict makes it a bit more "strict" and pretty much slaps you, if you are about to do something nasty in your script that could create a mess. An example is that without strict, you don't have to define variables first but can just write it out. This can cause issues with typos and such, which could lead to strange bugs that will be impossible, or very hard, to find. It's good for beginners.

<source lang=perl>
use warnings;
</source>

Does pretty much what it says. It gives you detailed information if it sees an error in your script when you run it, and outputs it to you. In some situations, it will even tell you exactly what is wrong. Always a good idea to use this, at least for debugging purposes.

<source lang=perl>
use CGI;
</source>

This loads a module for use in CGI, Common Gateway Interface. This is usually used when you want to make web development with perl. It's what making this script work

<source lang=perl>
use DBI;
</source>

Stands for DataBase Interface. Essentially it's the same thing as the CGI, except that it is for database use instead. This can connect, change, view, create databases of various kinds, like SQL, Oracle and more. A very powerful tool.

<source lang=perl>
use CGI::Carp qw(fatalsToBrowser);
</source>

You might have noticed that we have two calls for CGI. This one, however, only calls the functions for Carp with fatalsToBrowser. So to make sure that there is absolutely no chance of messing up, I included a call for normal CGI and then just this one.

<source lang=perl>
print CGI::header();
</source>

What this does, is to define the Content-type in the html code it is going to create through CGI. It essentially makes the script a webpage by defining this.

<source lang=perl>
my $username = dbquote(CGI::param('user'));
my $status = dbquote(CGI::param('status'));
my $password = dbquote(CGI::param('password'));
my $uid = dbquote(CGI::param('uid'));
my $gid = dbquote(CGI::param('gid'));
my $dir = dbquote(CGI::param('dir'));
my $upload = dbquote(CGI::param('upload'));
my $download = dbquote(CGI::param('download'));
my $comment = dbquote(CGI::param('comment'));
my $ipaccess = dbquote(CGI::param('ipaccess'));
my $quotasize = dbquote(CGI::param('quotasize'));
my $quotafiles = dbquote(CGI::param('quotafiles'));
</source>

What this does is define our variables. 'my' "creates" them and the dollar sign ($) defines that it's a variable that will only hold one value. In perl, it is called a scalar. The equal shows it what kind of variable it should be defined with. dbquote fetches a value, which it does inside it's parentheses. CGI::param'value' will get filled out later on with a value of some kind, through the script. Notice that the "params", the parameters, all have different names. This is what is used in the HTML page. Make sure these add up.

<source lang=perl>
unless($username) {
print <<PAGE;
<h1>Add a FTP account</h1>
<form action=testadddatabase.pl method=post>
Username: <input type=text name=user><br>
Status: <input type=text name=status><br>
Password: <input type=text name=password><br>
User ID: <input type=text name=uid><br>
Group ID: <input type=text name=gid><br>
Home Dir: <input type=text name=dir><br>
Upload Limit: <input type=text name=upload><br>
Download Limit: <input type=text name=download><br>
Comment: <input type=text name=comment><br>
IP Access: <input type=text name=ipaccess><br>
Quota Size: <input type=text name=quotasize><br>
Quota Files: <input type=text name=quotafiles><br>
<input type=submit value="Add an FTP account">
</form>
PAGE
</source>

This creates a website inside the script you are running. This makes it so you don't have to have a HTML page that links to this form. It essentially makes a frontend to the script.

<source lang=perl>
unless($username) {
</source>

This checks what "value" is being passed about. If it already had some information (i.e. the form has already been used), it won't call forth the form. If there is nothing, it will. The "{" starts the "form script" itself.

<source lang=perl>
print <<PAGE;
<h1>Add a FTP account</h1>
<form action=testadddatabase.pl method=post>
Username: <input type=text name=user><br>
Status: <input type=text name=status><br>
Password: <input type=text name=password><br>
User ID: <input type=text name=uid><br>
Group ID: <input type=text name=gid><br>
Home Dir: <input type=text name=dir><br>
Upload Limit: <input type=text name=upload><br>
Download Limit: <input type=text name=download><br>
Comment: <input type=text name=comment><br>
IP Access: <input type=text name=ipaccess><br>
Quota Size: <input type=text name=quotasize><br>
Quota Files: <input type=text name=quotafiles><br>
<input type=submit value="Add an FTP account">
</form>
PAGE
</source>

Trillex small business server 2008

2009-09-22T06:12:23Z

Trillex:

= Deployment of Small Business Server 2008 =<br>

THIS IS AN UNDERGOING PROJECT. MOST THINGS, IF NOT ALL, WILL CHANGE DURING THIS WEEK!

IF YOU SEE AN ERROR, CONTACT ME.

== Introduction ==

For this week, I am going to deploy a Small Business Server 2008, that would be suitable for a "standard" business.

Just to give me some kind of aim, I will put up these demands for myself:

The company got 15 computers. They require logins that goes through an exchange server. As any normal company, they also require emails, a website, personal login and a means of getting their files stored remotely on the server. A VPN connection for the workers as well as a means to manage the server remotely could also be mandatory.

== Small Business Server 2008 ==

Microsoft have developed this branch of server operating systems to benefit smaller business that does not require big servers. By doing this, they've made a cheaper license that most business can afford with the ability to update.

=== Limitations and Requirements ===

Windows Small Business Server 2008 got certain restrictions. This is because Microsoft wanted this to fit, as the name says, a small business so they put in some limitations to make the server operating system cheaper. Most business will not affected by these limitations. A lot of the limitations, like specific amount of space for emails, can be managed by implanting business policies - such as making sure you keep a tidy email account.

These limitations are:

*Only one SBS server in a domain. The domain can only handle more servers if these are of a different operating system, i.e. like linux, Windows Server etc.
*SBS is very picky about domains. It can only handle one and no child domains.
*Must be the root of the Active Directory forest.
*It is limited to 75 users (licenses).
*Earlier versions of SBS were limited to max 4 GB of memory. SBS 2008 requires a minimum of 4 GB and got a maximum limited of 32 GB. This is due to earlier versions being based on the x86 (32 bit) architecture while 2008 is based on x86-64 (64 bit). This change is because of Exchange Server 2007 is running in 64 bit.
*There are two different versions of SBS 2008. Standard Edition and Premium Edition. The difference between the two are: Premium includes a license to another Windows Server as well as MSSQL database.
*I am not certain if this limitation is still active in 2008 - but in Small Business Server 2003 service pack 2, the Exchange server limits you to 75 GB of emails.

If the business suddenly hits one of these limitations and needs to grow even further, it is possible to upgrade to a bigger license.

=== Installation of Small Server Business 2008 ===

Everybody knows how to press next and fill it out. So I will only fill this out with information that deems necessary to this project.

==== Partitioning ====

Normally, a server will have several harddrives in it and will run a certain kind of raid. Some people like to partition their harddrives to make it more "manageable" because they can assign certain drive letters to specific things, like documents for users etc. This is not at all necessary but can be easier to mange for certain people. I have decided not to do it - simply because it is not needed. By doing it this way, you will also force yourself to "read" drive/folder layouts and optimize them properly. This might be a linux thing but I prefer it this way.

In short, it's a matter of preference.

==== Updating and Virus Protection ====

Throughout the installation, it asks us whether or not we want to keep it up to date with updates and install it's virus scanner. We might as well, eh? Don't do it if you plan on using another one.

==== Post-installation ====

For the love of everything, remove UAC at once. It will make you hate everyone. Do that now.

== Network Diagram ==

This network diagram is suited for a very standard small business.

Note that since I do not have access to a computer with two ethernet interfaces, I have made it so I will not require this on the diagram. This can be a problem for certain businesses, since you cannot set up a proper firewall or monitor internet activity etc., except through a router's very limited monitoring tools and firewall.

[[Image:Sbs2008.png]]

It can be done in many ways, but this is a pretty good one for what we got.

Router goes to the internet and goes into a switch, which is connected to another switch and the server. The other switch is connected with all the computers. Remember that this is not how it will look physically. The IPs are guidelines. Obviously we can't have 244ish IPs since SBS only supports up until 75. Just giving it a range, is all.

Trillex small business server 2008

2009-09-22T06:09:00Z

Trillex:

Trillex small business server 2008

2009-09-21T12:32:11Z

Trillex:

File:Sbs2008.png

2009-09-21T12:26:17Z

Trillex: uploaded a new version of "Image:Sbs2008.png"

Network Diagram - Project - Small Server Business

Trillex small business server 2008

2009-09-21T12:10:09Z

Trillex:

Trillex - programming in perl with cgi and dbi

2009-09-21T11:46:40Z

Trillex:

Trillex - programming in perl with cgi and dbi

2009-09-21T11:41:17Z

Trillex:

Trillex - programming in perl with cgi and dbi

2009-09-21T11:07:12Z

Trillex: