Our new Indie Games subforum is now open for business in G&T. Go and check it out, you might land a code for a free game. If you're developing an indie game and want to post about it, follow these directions. If you don't, he'll break your legs! Hahaha! Seriously though.
Our rules have been updated and given their own forum. Go and look at them! They are nice, and there may be new ones that you didn't know about! Hooray for rules! Hooray for The System! Hooray for Conforming!
I work for a small company, handling tech-support and updating the website. My boss has asked me to look into creating an Intranet to "facilitate communication."
How do I create this Intranet that only the people within the organization can access? My Google searches pretty much return one of two things:
1) "Here's how you make a website, hur hur. Now, make that yer Intranet! How? You make a website, weren't ya readin'?"
2) "Use SharePoint."
I know how to make a website, but it's the "only people in the building can access it" part that I'm struggling with. My boss tried SharePoint 2007 before I came to work here, but no one used it, so he doesn't want to use it.
Any resources/suggestions would be greatly appreciated (preferably in the free or close-to-free price range ).
It would help to understand how your network is currently set up. Are you small enough that it's something like a home network -- ISP (cable/dsl) to a home-network type router to your machines? What is the IP range the machines are on in your network? Basically, if the machines on your network are already in a private IP range (192.168.1.0 for example), this is super easy -- you don't really need to do anything, just put the server you're using as a host on that network and don't set up the router to forward any ports to it (i.e. don't do anything), and you should be fine. For extra security, there's probably something in your router that will let you tell it not to let that server out to the internet (which you can take out when you need to do patching etc. and otherwise only let it communicate to the hosts already on your network).
Not knowing much about your network - the first thought is hosting it locally and putting it behind the firewall.
Ding. Couple that with hooking into whatever sort of domain authentication you're running, and allowing only internal traffic, and bam, y'all done got yerself a simple intranet. I have a feeling your boss wants to have basically an internal company webpage that can be used as a homepage/announcement portal/company blog. That's fairly easy stuff.
Really, you're just making a web server that's only going to talk to the internal network.
Looking for a DX:HR OnLive code for my kid brother.
Can trade TF2 items or whatever else you're interested in. PM me.
If it's internal use only, then just creating a webserver on an existing server is the easiest bet. As long as you don't forward anything external to it in your firewall, it'll stay intranet.
If it's just for internal communication you could always just setup a wiki on it. There are plenty of resources online for doing that on a simple IIS setup with windows.
If it's internal use only, then just creating a webserver on an existing server is the easiest bet. As long as you don't forward anything external to it in your firewall, it'll stay intranet.
If it's just for internal communication you could always just setup a wiki on it. There are plenty of resources online for doing that on a simple IIS setup with windows.
Additionally, to know what exactly you need, you need to know what exactly they want to do with it. Wikis are great for centrally storing information like Standard Operating Procedures or commonly used forms and that sort of thing, but if they want something that stores customer contact info or holds calendars for scheduling appointments and that sort of thing, something like SugarCRM (an open source Customer Relationship Manager) might be where you want to go, or even a combination of both (both run off web servers with a MySQL Database). The power of the system required to run these is entirely dependent on how many users access it and how often. For 10-20 users, you probably have a spare workstation around that could run a LAMP server (Linux-Apache-MySQL-PHP, the softwares commonly needed for these sorts of application; there are also WAMP servers, which are the same except on a Windows platform).
If you have to ask this question you will want to pay someone to do it for you, or at least consult with you on the project. I'm really not trying to be a jerk (though Thanatos will probably disagree with that), but a production environment at your place of employment isn't the proper place to learn how to do something as easy to screw up as deploy a corporate Intranet.
Back in the day, bucko, we just had an A and a B button... and we liked it.
If you have to ask this question you will want to pay someone to do it for you, or at least consult with you on the project. I'm really not trying to be a jerk (though Thanatos will probably disagree with that), but a production environment at your place of employment isn't the proper place to learn how to do something as easy to screw up as deploy a corporate Intranet.
It depends on the scope. If the boss just wants a homepage that people will see with the corporate logo/slogan/inspirational message of the day, then I don't think he needs to contract out for that.
If they want Real-Time Convergence with Interactive Whiteboard Application Sharing and Other Buzzwords We Heard About From This Conference that All Sound Really Cool, then yes, contract out and stay the fuck away from the time-and-money-sink unless you're asked to meddle.
edit - I'm not trying to be a jerk either, in case this needs to be stated for some reason, you'd know if I was trying
Looking for a DX:HR OnLive code for my kid brother.
Can trade TF2 items or whatever else you're interested in. PM me.
Yep. Set up a webserver on an internal PC. Depending on the platform you use and how comfortable you are with it, you can simply browse to said intranet using internal IP addresses, or you can get cute and map names if you like. As long as you don't forward in anything from the outside world, you're golden.
Be careful, though - you can absolutely open yourself up to some nice vulnerabilities if you don't watch what you are doing.
If you have to ask this question you will want to pay someone to do it for you, or at least consult with you on the project. I'm really not trying to be a jerk (though Thanatos will probably disagree with that), but a production environment at your place of employment isn't the proper place to learn how to do something as easy to screw up as deploy a corporate Intranet.
It depends on the scope. If the boss just wants a homepage that people will see with the corporate logo/slogan/inspirational message of the day, then I don't think he needs to contract out for that.
If they want Real-Time Convergence with Interactive Whiteboard Application Sharing and Other Buzzwords We Heard About From This Conference that All Sound Really Cool, then yes, contract out and stay the fuck away from the time-and-money-sink unless you're asked to meddle.
Well, the OP asked the question more from a security standpoint (how to limit access to internal users), so I (personally) would more carefully consider the sensitivity of the information being handled rather than the complexity of the functionality provided in making a decision to bring someone in (if I were in his shoes). Regardless of the complexity of the application, if it's dealing with information like PII or PHI (such as an HR application would), it would probably be best to consult someone about the secure development and deployment of the application. If the OP doesn't know what PII or PHI are, then he should definitely bring in someone to consult about the development and deployment of the application. Do this during the development process - security isn't something you can bake on after a solution is deployed. But now we're getting into an SDLC and/or a C&A discussion and it all just gets very boring from here (and probably not applicable).
EDIT: I really really need to take a vacation.
Back in the day, bucko, we just had an A and a B button... and we liked it.
If you have to ask this question you will want to pay someone to do it for you, or at least consult with you on the project. I'm really not trying to be a jerk (though Thanatos will probably disagree with that), but a production environment at your place of employment isn't the proper place to learn how to do something as easy to screw up as deploy a corporate Intranet.
It depends on the scope. If the boss just wants a homepage that people will see with the corporate logo/slogan/inspirational message of the day, then I don't think he needs to contract out for that.
If they want Real-Time Convergence with Interactive Whiteboard Application Sharing and Other Buzzwords We Heard About From This Conference that All Sound Really Cool, then yes, contract out and stay the fuck away from the time-and-money-sink unless you're asked to meddle.
edit - I'm not trying to be a jerk either, in case this needs to be stated for some reason, you'd know if I was trying
Basically this. He wants to put links to inspirational videos and links. Aye yie yie.
If you have to ask this question you will want to pay someone to do it for you, or at least consult with you on the project. I'm really not trying to be a jerk (though Thanatos will probably disagree with that), but a production environment at your place of employment isn't the proper place to learn how to do something as easy to screw up as deploy a corporate Intranet.
It depends on the scope. If the boss just wants a homepage that people will see with the corporate logo/slogan/inspirational message of the day, then I don't think he needs to contract out for that.
If they want Real-Time Convergence with Interactive Whiteboard Application Sharing and Other Buzzwords We Heard About From This Conference that All Sound Really Cool, then yes, contract out and stay the fuck away from the time-and-money-sink unless you're asked to meddle.
edit - I'm not trying to be a jerk either, in case this needs to be stated for some reason, you'd know if I was trying
Basically this. He wants to put links to inspirational videos and links. Aye yie yie.
Well in that case, make sure you punk them with goatse.
Back in the day, bucko, we just had an A and a B button... and we liked it.
It depends on the scope. If the boss just wants a homepage that people will see with the corporate logo/slogan/inspirational message of the day, then I don't think he needs to contract out for that.
Basically this. He wants to put links to inspirational videos and links. Aye yie yie.
Ok then this is dead simple. Pick a server with some free cycles/storage. Download and install the free windows sharepoint services. Note that this isn't the same as sharepoint server, but it's built on the same core. Think MSDE vs SQL server.
This will give you what he wants, it runs pretty well right out of the box with default settings, plus you get to put some sharepoint admin experience on your resume.
Posts
http://steamcommunity.com/profiles/76561198006524737
Ding. Couple that with hooking into whatever sort of domain authentication you're running, and allowing only internal traffic, and bam, y'all done got yerself a simple intranet. I have a feeling your boss wants to have basically an internal company webpage that can be used as a homepage/announcement portal/company blog. That's fairly easy stuff.
Really, you're just making a web server that's only going to talk to the internal network.
Can trade TF2 items or whatever else you're interested in. PM me.
If it's just for internal communication you could always just setup a wiki on it. There are plenty of resources online for doing that on a simple IIS setup with windows.
Unofficial PA IRC chat: #paforums at irc.slashnet.org
Additionally, to know what exactly you need, you need to know what exactly they want to do with it. Wikis are great for centrally storing information like Standard Operating Procedures or commonly used forms and that sort of thing, but if they want something that stores customer contact info or holds calendars for scheduling appointments and that sort of thing, something like SugarCRM (an open source Customer Relationship Manager) might be where you want to go, or even a combination of both (both run off web servers with a MySQL Database). The power of the system required to run these is entirely dependent on how many users access it and how often. For 10-20 users, you probably have a spare workstation around that could run a LAMP server (Linux-Apache-MySQL-PHP, the softwares commonly needed for these sorts of application; there are also WAMP servers, which are the same except on a Windows platform).
It depends on the scope. If the boss just wants a homepage that people will see with the corporate logo/slogan/inspirational message of the day, then I don't think he needs to contract out for that.
If they want Real-Time Convergence with Interactive Whiteboard Application Sharing and Other Buzzwords We Heard About From This Conference that All Sound Really Cool, then yes, contract out and stay the fuck away from the time-and-money-sink unless you're asked to meddle.
edit - I'm not trying to be a jerk either, in case this needs to be stated for some reason, you'd know if I was trying
Can trade TF2 items or whatever else you're interested in. PM me.
Be careful, though - you can absolutely open yourself up to some nice vulnerabilities if you don't watch what you are doing.
[SIGPIC][/SIGPIC]
Well, the OP asked the question more from a security standpoint (how to limit access to internal users), so I (personally) would more carefully consider the sensitivity of the information being handled rather than the complexity of the functionality provided in making a decision to bring someone in (if I were in his shoes). Regardless of the complexity of the application, if it's dealing with information like PII or PHI (such as an HR application would), it would probably be best to consult someone about the secure development and deployment of the application. If the OP doesn't know what PII or PHI are, then he should definitely bring in someone to consult about the development and deployment of the application. Do this during the development process - security isn't something you can bake on after a solution is deployed. But now we're getting into an SDLC and/or a C&A discussion and it all just gets very boring from here (and probably not applicable).
EDIT: I really really need to take a vacation.
Basically this. He wants to put links to inspirational videos and links. Aye yie yie.
Well in that case, make sure you punk them with goatse.
Ok then this is dead simple. Pick a server with some free cycles/storage. Download and install the free windows sharepoint services. Note that this isn't the same as sharepoint server, but it's built on the same core. Think MSDE vs SQL server.
This will give you what he wants, it runs pretty well right out of the box with default settings, plus you get to put some sharepoint admin experience on your resume.