I don't need IT, ipads fuck ralara every day (IT thread)

[halbarad]

I'm trying to get a PAC file working to allow staff laptops to be used in school (currently they can't really get internet access as our Managed Services people are a bunch of idiots and don't want to give out the WPA key for the WiFi they specifically set up for staff usage), which requires them to go through the school firewall/filter system and for the laptops to work normally at home. I've got a basic idea of how it works and a file I've tested but doesn't work:

function FindProxyForURL(url, host)
{
return "PROXY 10.174.52.29:8080; DIRECT";
}

From everything I've read online that should work fine, it should try the first proxy address and if that fails then resort to a direct connection. IE throws up a "Cannot display webpage" error when I try it but if I put the proxy in the manual settings then it works fine.

Is there anything obviously wrong with the code or is it just IE playing silly buggers? I haven't tried FF or Chrome yet as IE is the main thing staff will be using due to some needed functionality in our VLE that is only supported by IE.

EDIT: Nevermind, was being an idiot and forgetting to include "file://" before the path to PAC in the Internet Settings.

[smagd]

EDIT: Nevermind, was being an idiot and forgetting to include "file://" before the path to PAC in the Internet Settings.

Also, you posted this in the wrong thread.

[El Capitano]

it is mind bogglingly amazing how few people can do Database normalization half-way decently Batolemaeus, so pay attention tbh...

Database normalisation is easy, it's getting it to perform decently afterwards that's the problem.

[XenosisReaper]

Fuck Windows 7 Group Policy gubbins.

Fuck it to hell.

[Ben Derindar]

Database normalisation is easy, it's clients changing their minds on entire relationship structures after the db has already been set up to the original spec that's the problem.

FYP.

[Daneel Trevize]

it's clients... that's the problem.

FYP.

FYP

[Lana Torrin]

Today I started to learn powershell.. Why did you have to make it hard microsoft?

[Vaksai]

Today I started to learn powershell.. Why did you have to make it hard microsoft?

Powershell is easy, but since I'm getting a free Galaxy Nexus, I might as well go on a 3-day course, paid by my boss.

[smagd]

Database normalisation is easy, it's clients changing their minds on entire relationship structures after the db has already been set up to the original spec that's the problem.

FYP.

+1

From a project I was involved in:

V1. Each article has a different price.
V2. Each article has a different price per supplier and warehouse.
V3. Each article has a different price per supplier and warehouse depending on the region it's being ordered from.
V4. Each article has a different price per supplier and warehouse depending on the region it's being ordered from and the purpose it's being used for.
V5. There are sets of articles, but they can only be delivered if all components can be delivered for the given combination of supplier, warehouse, region and purpose.
V6. Articles have minimum packing sizes. Add missing articles even for sets for the best price that was current when the original order was fulfilled.

I'm kinda curious what they'll come up with next. I figure it could be fun to add bulk prices, for instance.

[Stoffl]

Fuck you SAP Web Client.

That is all.

[IceBlock]

For all the whiners out there, why not bring forth your problem so one can compare and in worst case scenario actually provide a solution?

[lubica]

For all the whiners out there, why not bring forth your problem so one can compare and in worst case scenario actually provide a solution?

Also, it's more entertaining for the rest of us

[Apoplexy]

Our leased line contract with BT is up; apparently we're going to be moving to TalkTalk to "save money".

This must mean that the hundreds of e-mails we send/receive every day and the online banking services we're implementing, are not as important as I was led to believe.

[kzig]

Light at the end of the tunnel?

Man, I'm glad a big company (Atos) has had the balls to point out to people that there can be a better option than email.
But it's gonna be a long fucking time before all the old people using computers go away so we can stop pretending like all internal mails need to be treated like business letters to eachother.

Another step towards decentralised IT:

http://www.bbc.co.uk/news/business-16486796

[Mimiru]

Apparently it takes companies a while to sign multimillion dollar web design/dev/hosting deals, meaning I have fuck all to do at work :/ At least they'll be fun projects. USE ALL THE CLOUDS (projects use azure, ec2, and a private vCloud) :v All of the other projects i'm the lead on are winding down as well, sadface.

In the mean time, i've seemed to take over the role of TFS admin for my team of ~40 devs :/. Teaching UID interns how to use visual studio/tfs is ughhhh.

[Shaikar]

Apparently it takes companies a while to sign multimillion dollar web design/dev/hosting deals, meaning I have fuck all to do at work :/ At least they'll be fun projects. USE ALL THE CLOUDS (projects use azure, ec2, and a private vCloud) :v All of the other projects i'm the lead on are winding down as well, sadface.

In the mean time, i've seemed to take over the role of TFS admin for my team of ~40 devs :/. Teaching UID interns how to use visual studio/tfs is ughhhh.

TFS, ouch. I think the best feature of TFS is its uninstall.

[Mimiru]

haha. They only difficult part is getting folks to remember tom ake sure the damn .csproj files get checked in when adding/deleting items.

Also, for most projects we have continuous integration so it builds and deploys to dev on every check in. Sometimes it shits itself on the deployment steps when a bunch of people check stuff in at once.

Other than that the sharepoint integration and reporting is pretty nice i guess.

[Liare]

Light at the end of the tunnel?

Man, I'm glad a big company (Atos) has had the balls to point out to people that there can be a better option than email.
But it's gonna be a long fucking time before all the old people using computers go away so we can stop pretending like all internal mails need to be treated like business letters to eachother.

Another step towards decentralised IT:

http://www.bbc.co.uk/news/business-16486796

of course, actually using the cloud is problematic at best, the rules and regulations around sensitive information wear black nazi uniforms for a reason, no matter how inconvenient google might find that.

sorry, cloud shit makes me rage hard, especially as it equates to giving another company the keys to your holiest of holy and it continues to astound me that people want to use that junk, especially with sensitive information like customer data and so forth.

i am cool with putting stuff like the corporate web-page that only serves as a "call this number/email this address to get in touch" into the "cloud" but office email ? corporate data ?

pass me that bong, because that must be some really good stuff!

(about the only "cloud" stuff i approve of is the in-house "private" cloud using things like ESX with a vSphere on top, but that's not really cloud computing. just server virtualization)

[erichkknaar]

Light at the end of the tunnel?

Man, I'm glad a big company (Atos) has had the balls to point out to people that there can be a better option than email.
But it's gonna be a long fucking time before all the old people using computers go away so we can stop pretending like all internal mails need to be treated like business letters to eachother.

Another step towards decentralised IT:

http://www.bbc.co.uk/news/business-16486796

of course, actually using the cloud is problematic at best, the rules and regulations around sensitive information wear black nazi uniforms for a reason, no matter how inconvenient google might find that.

sorry, cloud shit makes me rage hard, especially as it equates to giving another company the keys to your holiest of holy and it continues to astound me that people want to use that junk, especially with sensitive information like customer data and so forth.

i am cool with putting stuff like the corporate web-page that only serves as a "call this number/email this address to get in touch" into the "cloud" but office email ? corporate data ?

pass me that bong, because that must be some really good stuff!

(about the only "cloud" stuff i approve of is the in-house "private" cloud using things like ESX with a vSphere on top, but that's not really cloud computing. just server virtualization)

I agree. The move to the cloud usually comes from groups getting pissed off with IT under/slow delivery (which is valid) or simply someone in management getting hip to the hype that surrounds it. 9 out of 10 times, these groups don't know the first thing about infosec so you end up with all kinds of stuff deployed onto Amazon that should really be kept inside the firewall. WE've been using Eucalyptus on top of Xen for private cloud and we're now just starting to research OpenStack. Eucalyptus works well, and private cloud is a solid deployment model if you take enough care to implement it properly. Having said that though, ESX doesn't scale well for cloud, from a money point of view.

[kzig]

Confirming that pretty much everyone at my workplace harbours nothing but resentment towards IT due to the glacial pace of change, and that cloud is being considered as an alternative for most of what we do. Examples include:

• Quoted timescale of 2-3 years to make even a small change to our main website
• Quoting 10x the market rate to set up some modelling servers (our department decided to rent external servers instead).
• Procurement of PCs with graphics cards capable of running GIS software so slow that the head of department gave up and went on a shopping spree at PC world - an entire team of people now have stand-alone PCs just for running GIS.
• 1 year or more to get official approval for the use of any new piece of software.
• New employees waiting up to 1 month from time of application to be granted database access (preventing them from doing any significant work).
• Catch-22 database access request process (you can't be granted access unless you specify the exact database path, and IT does not publish any details of which databases are located where)
• Typical delay of 5 working days to dispatch someone to fix a non-booting PC (we don't hot-desk and nearly every PC is in use).
• Random assortment of ageing desktops - most PCs are at least 3 years old, and others are 6-7 years old (Pentium IV with 512mb of ram anyone?).

I haven't worked anywhere else for any significant period of time - how does this compare to other peoples' experiences?