|
Tgent posted:Not sure if this is the right place to ask this, but here goes anyway. Can anyone give some advice on how I might deploy different print drivers for the same printer depending on AD groups? I need to lock most users out of colour printing, so I've found a custom driver which does just that. Problem is the driver has the same name as the standard driver, and If I add it in print management it just overwrites the standard driver resulting in no one at all being able to print in colour. Is there a way around this? Does the printer driver offer any kind of security for color printing? That's how we manage it. Our larger Multi Function Devices all have an area where you have to put a numerical code in that allows certain permissions.
|
#
?
Jul 22, 2015 02:13
|
|
|
|
| # ? May 14, 2024 19:55 |
|
|
I just disabled 2.5k active users via VBScript. That's enterprise as gently caress and feels awesome 
|
|
#
?
Jul 22, 2015 02:42
|
|
|
Tony Montana posted:I just disabled 2.5k active users via VBScript. That's enterprise as gently caress and feels awesome VBScript is enterprise as gently caress?
|
|
#
?
Jul 22, 2015 02:43
|
|
|
Tony Montana posted:I just disabled 2.5k active users via VBScript. That's enterprise as gently caress and feels awesome Please for the love of gently caress use PowerShell
|
|
#
?
Jul 22, 2015 02:55
|
|
|
I'm looking for some good windows security blogs to keep me and my team up to date on things like that critical font issue on the previous page. Any suggestions? Also every time I say I'm done with vbs, another vbs task comes my way. It's awful.
|
|
#
?
Jul 22, 2015 03:12
|
|
|
Internet Explorer posted:VBScript is enterprise as gently caress? Very much so. You'll find many logon scripts, application scripts.. heaps of stuff still written in VBS. Your ability to bounce between that and PS without blinking makes you an Automation Lead, which is enterprise as gently caress. Not just a guy that can write a quick and dirty script (which should be all of you), but the guy you point at the thousand line logon script that's grown over the last decade and he turns it into a beautiful example of best practice and legibility. You also leave him alone for a few weeks to do this. Pretty soon you'll have application teams hearing about your mad skillz and you'll be getting Lync popus from all over the world asking if you've got a couple of minute to take a look at the mess their in. This is how you carve your niche somewhere big and pretty soon you just have a monthly meeting with your TL who asks 'are you doing heavy poo poo still?' and you say 'yeah, man' and you're left completely alone otherwise. Powershell is the new kid on the block, but an established Windows enterprise network has been doing their thing probably for a lot longer than Powershell has been around for. VBS means you speak the old and the new language  CLAM DOWN posted:Please for the love of gently caress use PowerShell hehe, no mate. Powershell works great for simpler operations, but it's a .NET based language while the API for things like Excel is still .COM. If you're writing complex code with many programmatic structures like nested statements and interacting with .COM APIs, VBS still is king for many things. A smaller place you can decree Powershell and try and outlaw VBS, but anywhere really large (i.e. an enterprise) and that's just not reasonable. I will tell you a story, so my old role was writing automation for Active Directory for Hewlett Packard. Another advantage of VBS is I don't need to turn on 'Remote Code Execution' which you do for PS, a VBS script will just run anywhere on a Windows network (yes, you should be alarmed if you didn't know this). So I had a huge energy company who wanted a pile of fun with their AD and I wanted script it all, but there were 2003 DCs (which PS wasn't going to run natively on) and you'd have to go through the change control of enabling remote code execution on all the domain controllers. Obviously.. this is a hard thing to get past a risk adverse change control board. With VBS I don't change anything, everything runs everywhere and I can do everything Powershell does and more. Does VBS still run natively on all Windows operating systems? Yes (certainly the ones you're going to run into anyway). In this role I re-wrote much of my HP work in PS for this employer. Depending on the task I'll use either, but big operational stuff where I'm generating reports in Excel, etc, VBS is still my goto. edit: Just to make this point even more, the job I'm really hoping I get is as a VBS scripter for the Australian Department of Defence. Great pay, conditions.. etc. Remember the really big networks of this world perhaps aren't as ready to embrace the new and chuck out the old as Microsoft marketing would like you believe. Tony Montana fucked around with this message at 03:24 on Jul 22, 2015 |
|
#
?
Jul 22, 2015 03:19
|
|
|
You're an odd one and sound like you've been around in the industry for a while and I respect that, but you're making a lot of assumptions and are a little outdated. I work for a large enterprise in Canada and focus on security, I'm not comfortable posting more details than that. We have absolutely done away with vbs, and thanks primarily to my efforts use PowerShell 4 environment wide (excluding a handful of server 2003 relics that are well isolated and rightfully ignored). If you're needing COM/Excel related things, guess what, PS can do that! You're doing yourself a massive disservice not moving over to it. It's the single greatest tool in an enterprise Windows admin's kit.
|
|
#
?
Jul 22, 2015 03:45
|
|
|
Why am I an odd one? What did I say that was outdated? I have moved to Powershell, I said that, but my experience means I bring more to the table than someone who started with Powershell. COM with PS is slow, I can link the scripting guy articles that covers this when I get back to the office of you like. Maybe you've done away with VBS in your environment, but there is plenty still out there.
|
|
#
?
Jul 22, 2015 04:03
|
|
|
It was more your comments that PowerShell is for simpler or smaller environments, which is patently false. True enough though, about com objects
|
|
#
?
Jul 22, 2015 04:06
|
|
|
I didn't mean that at all, if that's how it sounded then you're right to call it out. I more meant that eradication of VBS hasn't happened anywhere really big I've worked. If you managed it, then good on you, but if someone says they're an experienced VBS scripter don't snort with derision. It can still mean a whole lot in 2015
|
|
#
?
Jul 22, 2015 04:10
|
|
|
peak debt posted:Machines also need to log in in AD before they're allowed to verify passwords. So it seems that you have problems with the client identifying itself to the server. I'm not sure if this is possible in EC2, but what I'd try next is whether the client can access a server share. Also, even if you don't have proper certificates, you should still make a domain trusted certificate. Server 2012 can create those even in the Standard version. Then you can manually import the root certificate on the client and you won't get any scary IE messages about invalid certificates that might demote your security zones. Thanks a lot, this looks like it could get it to wrok! I'll try this out at some point but I had to put this stuff on hold for now as it wasn't super critical and I had other poo poo to figure out.
|
|
#
?
Jul 22, 2015 10:28
|
|
|
I just yelled at my coworker "WHO KICKED ME OFF MY RDP SESSION!" only to discover I kicked myself off bc I forgot I logged in on another computer just windows admin things!
|
|
#
?
Jul 22, 2015 14:29
|
|
|
This is probably a dumb question, but I am a developer stuck with random admin duties because my boss refuses to accept that we need to hire an admin instead of just more programmers. I have a very poor understanding of how window licensing, and specifically volume licensing, works. We have a Windows Server 2008 R2 enterprise MAK. It says we've used 11 of 45 activations. Does that mean I can set up 34 more servers with Windows Server 2008 R2? I don't happen to have any extra servers just lying around or need to set up any more, I was just wondering. It seems like an awfully large number for us to have purchased unless I am understanding it wrong.
|
|
#
?
Jul 22, 2015 16:13
|
|
|
wilderthanmild posted:This is probably a dumb question, but I am a developer stuck with random admin duties because my boss refuses to accept that we need to hire an admin instead of just more programmers. I have a very poor understanding of how window licensing, and specifically volume licensing, works. We have a Windows Server 2008 R2 enterprise MAK. It says we've used 11 of 45 activations. Does that mean I can set up 34 more servers with Windows Server 2008 R2? I don't happen to have any extra servers just lying around or need to set up any more, I was just wondering. It seems like an awfully large number for us to have purchased unless I am understanding it wrong. That's just activation. It doesn't represent how many licenses you own. It's so if you're doing testing you can create and delete servers at will. You can ask for more activations if you run out.
|
|
#
?
Jul 22, 2015 16:18
|
|
|
wilderthanmild posted:This is probably a dumb question, but I am a developer stuck with random admin duties because my boss refuses to accept that we need to hire an admin instead of just more programmers. I have a very poor understanding of how window licensing, and specifically volume licensing, works. We have a Windows Server 2008 R2 enterprise MAK. It says we've used 11 of 45 activations. Does that mean I can set up 34 more servers with Windows Server 2008 R2? I don't happen to have any extra servers just lying around or need to set up any more, I was just wondering. It seems like an awfully large number for us to have purchased unless I am understanding it wrong. Don't worry too much, no one understands Microsoft licensing. But activations does not equal licenses.
|
|
#
?
Jul 22, 2015 17:52
|
|
|
skipdogg posted:Does the printer driver offer any kind of security for color printing? That's how we manage it. Our larger Multi Function Devices all have an area where you have to put a numerical code in that allows certain permissions. I had a look and the printer driver allows you to disallow color printing outright which is good enough for me. Thanks!
|
|
#
?
Jul 23, 2015 00:50
|
|
|
Heard Filemaker mentioned here as decent for Asset/License tracking trying to get it set up to do that and handle our new hire requests to keep track of what hardware/software stuff we give them. The asset starter solution is okayish but doesn't handle the people side well is there a good solution people use or should I just build something from scratch? Doesn't have to be free I can justify the expense if it saves me time.
|
|
#
?
Jul 23, 2015 01:11
|
|
|
I haven't screwed around with VBScript at all, but from what I've heard it's a lot harder to use and slower to write. I have a couple of You could probably call the COM VBScript-lets from powershell if those parts really are faster. I haven't tried running a sort of mixed mode though. What about maintainability of your code? Newbies probably don't even know VBScript exists, let alone the syntax, etc. I guess it's good job security. The guy I replaced has a bunch of cryptic cmd and bat scripts that more or less run our department. Some of them are over six pages long and have been replaced with less than 20 lines of powershell.
|
|
#
?
Jul 23, 2015 01:17
|
|
|
Well, I write Powershell as I said above. But VBS is pretty close to actual VB, which is a programming language and not a scripting language. That means what you probably think it means, it's less focused on you being able to easily pick it up and do things with little training and more focused on supporting large and complex structures in-line with programming standards. VBS isn't batch scripting at all. Another point is as specialist, my code isn't passed from support staff member to support staff member. I am employed to do my magic and I take my code with me, my code is for me alone. Obviously if I'm working on the logon script or an application team's script then yeah, we want to do it in the most understood and supportable way for the incumbent teams (Powershell if you guys are most comfortable with that, no problem). But most of the time as the AD Lead you'll be asked to perform large operations (such as I did yesterday) or produce complex reports and how you actually get there is up to you. This is similar to a consultant that comes in to handle a huge migration to O365.. you employ him and he comes in and does the job, unless you've specified it in his deliverables he's not then going to take a week to explain to you how he did it complete with nice, legible code for you to steal and reproduce. You can interact with COM objects from PS and I can even call VBS from PS, but I don't know how I could pass variables between the two (you probably can, I just don't know). So it's got nothing to do with job security, in fact if PS has a faster and better way to do something and I don't get on board then I'm the slow, cumbersome guy faffing around when the newer guy doing it in PS is getting it done. When you say 'newbie', I sit above L3 Wintel. So I only ever deal with L3 engineers who escalate to me, L2 escalates to L3 and L1 to L2. So I'll never deal with a 'new' IT person, if you haven't got a decade of enterprise experience behind you along with a pile of certs (an Uni degree helps too, you can see the difference every day between Uni grad and those that don't have it) then you're probably not L3 and probably not talking to me. The experienced guys know what I articulated above, VBS often still runs a heck of a lot in the world's biggest networks. So.. what am I doing in VBS then.. which is the question I'd be asking. Well for example reporting out of Active Directory. You can use Get-ADUser, sure, you can even pass it LDAP syntax to do complex queries. What I ran into when I was doing my porting from VBS though, was then passing that to Excel's API. I want to pull attributes, often do some complex operations on what comes out (because AD attributes in reality often don't look like anything you see in Users and Computers) and then pass them to an Excel spreadsheet. Not just stick it in there either, I want to be able to create multiple worksheets, generate graphs from the data.. basically make a really professional report that looks like some admin person spent a day in Excel whipping it up. Compared to CSV exports and other less sophisticated methods business staff just love the way I do reporting, they open up the spreadsheet and use the data manipulation features in it to further carve up the data into what they want. I have seen no tool produce reports like mine, the last two I've worked with being the Quest suite (now owned by DELL) and NetWrix. I'm pretty sure I ran into some limitations with string manipulation and other things, which were costing me a lot of time and I just wrote what I wanted in VBS because I knew how to do it. Just on the reporting side, with me on staff you don't need a Quest license.. and you can interact with my interface (i.e. talk to me) at a higher level (as in programming language levels) than you can interact with the tool's interface. We are talking about different kinds of scripting, mostly, and if I'm writing something for the rest of the team to use and to be passed around.. and you like Powershell.. then I'll write you some Powershell.
|
|
#
?
Jul 23, 2015 02:44
|
|
|
I still don't understand why you need login scripts using VBS. The whole world has moved passed login scripts. And the reporting you are doing can easily be done with Powershell, but in my opinion the correct way would be using SSRS. Honestly, you seem to continuously bring up the fact that you work for HP. I'm not sure that is worth bragging about. In my mind working for HP is the same as working IT for IBM, Cisco, or the government. It's a mark against, not a mark in your favor. And I'm fairly sure everyone here knows how Tier 1 / 2 / 3 work.
|
|
#
?
Jul 23, 2015 03:05
|
|
|
haha, yep working for the world's tier one vendors is a mark against you. This is the enterprise thread, right? edit: and hey, honestly, for you to say 'the whole world has moved passed logon scripts' is ridiculous. Ok, let's remove the nark and talk properly. Both my current network and my last employer had massive logon scripts in VBS. Yes, I'm the AD Lead so I want everything in GPO Preferences as much as possible, I prefer it there myself. But the simple reality is there are already huge VBS scripts in-place, that have been there for literally decades and with the increasingly influx of people that don't know anything but Powershell.. no-one really knows what these scripts do! Converting it all to PS sounds great, but it's a project, not BAU work, because it's pretty massive and if the script is working then management can spend those project dollars somewhere else. Both of these networks I'm talking about are over 10k seats and 1.5k production servers. It's big stuff, man, these are the kind of networks and businesses that can afford to pay you 150k and you get to play and have all the nicest toys. In my experience we keep running into this. Maybe in 10 years or something it literally will be all PS and that's great because I'll have another 10 years of PS experience behind me.. but I just keep running into VBS. It's put me in a powerful position being able to handle that and not shrug and ask if we can re-write it in something I understand. I also wrote an effort post a few pages back about working for HP and what it meant, if you didn't read it take a look. Best job I've ever had, mate, and I've had a few in this game. Tony Montana fucked around with this message at 03:33 on Jul 23, 2015 |
|
#
?
Jul 23, 2015 03:12
|
|
|
Yes, working for HP is a mark against you. Sorry.
|
|
#
?
Jul 23, 2015 03:29
|
|
|
I'm guessing you're American, so is that really how it's perceived in the States? I'm just asking the thread, if you had an ex-IBM or ex-HP guy would that be considered a negative? Is it because you perceive large vendors to be siloed and people that come from there aren't generalists? You can't just chuck random jobs at them and they'll happily just do whatever is put in front of them?
|
|
#
?
Jul 23, 2015 03:36
|
|
|
It doesn't matter to me who you worked for, but the way you're posting is very smug, condescending, and closed-minded. As you said, this is the enterprise Windows thread, it's safe to say there are a lot of enterprise Windows experts here who could even know more than you. Examine how you're coming across and stop blowing yourself up, no one gives a poo poo about HP outside the US either.
|
|
#
?
Jul 23, 2015 03:56
|
|
|
My current company has dozens of complex login scripts that sometimes get to be like 300 lines long. They were barely documented and mostly implemented in the 90's on Novell Netware. They are huge pain to deal with as any kind of change deals all kinds of headaches. As we finish up our migration off of Novell to a completely Microsoft shop this summer, one of the biggest casualties were these dumpster fire hell hole scripts that have been replaced with GPOs that map drives per department and change a few shortcuts for internal apps rather than scores of if/else and switch statements that was meant to make things 'easy' for the functional retarded people at my company. While the users haven't changed, we no longer cater to the lowest common denominator by over complicating everything, and just tell the user to learn it or GTFO. I know I'm not as ~~enterprise~~ as HP, but I think what everyone is saying here is that having an albatross of ridiculous login scripts is not typical in a modern environment, and probably isn't something to be bragging about.
|
|
#
?
Jul 23, 2015 03:59
|
|
|
Internet Explorer posted:working IT for IBM, Cisco, or the government. It's a mark against, not a mark in your favor Why?
|
|
#
?
Jul 23, 2015 04:45
|
|
|
CLAM DOWN posted:It doesn't matter to me who you worked for, but the way you're posting is very smug, condescending, and closed-minded. As you said, this is the enterprise Windows thread, it's safe to say there are a lot of enterprise Windows experts here who could even know more than you. Examine how you're coming across and stop blowing yourself up, no one gives a poo poo about HP outside the US either. I'm just posting about what I do, man. You can choose if you take offense to that. Perhaps I come across as condescending sometimes because I've read bullshit in here like 'no one gives a poo poo about HP outside the US either'. That is complete bullshit. Where else in the world have you worked to be able to say this? HP is huge in Australia, the Australian Tax Office and major banks are totally managed by HP. HP is huge in the UK, I interviewed in London for a HP gig. I get approached by recruiters frequently and they always want to know about my time at HP. Along with 'the entire world has moved on from logon scripts'. It's just not true. It sounds like an internal IT guy's opinions, where he really works in his own little bubble (often of his own making) and his experience is limited. I just challenge some of these statements I think are crap. Just like this VBS thing, if in your own world VBS is done away with.. ok, fine.. but to then postulate VBS is gone everywhere and it's never used just isn't true. You've also got a pretty clear agenda, you don't know VBS or don't want to so discrediting it and trying to drive it off wherever you can fits into the educational paths you've chosen. You simply can't do this in many of the large network's I've worked. But please, let's not detract from the awesome answer I'm waiting from IE for.. namely why the world's largest and best known vendors are actually the rear end-end of the industry.
|
|
#
?
Jul 23, 2015 05:14
|
|
|
Tony Montana posted:I'm just posting about what I do, man. You can choose if you take offense to that. Perhaps I come across as condescending sometimes because I've read bullshit in here like 'no one gives a poo poo about HP outside the US either'. That is complete bullshit. Where else in the world have you worked to be able to say this? HP is huge in Australia, the Australian Tax Office and major banks are totally managed by HP. HP is huge in the UK, I interviewed in London for a HP gig. I get approached by recruiters frequently and they always want to know about my time at HP. I'm not saying you're necessarily wrong, there is a TON of outdated stuff in large enterprises like VBS and I would very much value someone who knew it inside and out. I just have an issue with your loving attitude and smug generalizations and assumptions, which is why I wouldn't hire you, nothing to do with HP.
|
|
#
?
Jul 23, 2015 05:40
|
|
|
I would value someone who doesn't accept the status quo and challenges obvious bullshit when they see it. I'm not your subordinate or even your colleague. I am your peer, I'm not looking for job from you, I'm just looking for robust and intelligent discussion about enterprise Windows. Anyways, peace dude. I don't mean to piss you or anyone off. Let's keep this about the computing. I am going to go and write some Powershell :P \/\/ Thanks, man Tony Montana fucked around with this message at 06:02 on Jul 23, 2015 |
|
#
?
Jul 23, 2015 05:59
|
|
|
mayodreams posted:I know I'm not as ~~enterprise~~ as HP, but I think what everyone is saying here is that having an albatross of ridiculous login scripts is not typical in a modern environment, and probably isn't something to be bragging about. Not a modern but in legacy environment or some Fortune 500? I wouldn't be surprised and while their might be a better or new way to do things this method still works. Is there anything preventing login scripts from executing? As for bragging, I don't find his comments boisterous and sure HP isn't doing that well but I'm sure he works on the consulting side of the business not hardware.
|
|
#
?
Jul 23, 2015 06:01
|
|
|
Internet Explorer posted:In my mind working for HP is the same as working IT for IBM, Cisco, or the government. It's a mark against, not a mark in your favor. Working in enterprise IT environments is a bad thing? 
|
|
#
?
Jul 23, 2015 06:03
|
|
|
So hey... Did Microsoft say if they're going to officially release a Windows 10 iso at launch? And if so, how is it supposed to know I'm upgrading from Windows 7 / 8? My Win7 machines have OEM keys on them, my Win8 machines have keys in the Bios, but I'd really appreciate if they loving explain how it's going to work since it launches in less than a week. You'd think they'd just accept all Win7 OEM product keys as Win10 activations, but that still doesn't work in preview. I really hope they don't expect me to do non-clean installs of each machine to get the free upgrade.
|
|
#
?
Jul 23, 2015 14:44
|
|
|
I want to learn SCCM (and later, SCOM). Where should I start? I don't seem to be able to focus on just browsing the info on Technet (it's organized poorly IMO).
|
|
#
?
Jul 23, 2015 15:20
|
|
|
Gerdalti posted:I want to learn SCCM (and later, SCOM). Where should I start? I don't seem to be able to focus on just browsing the info on Technet (it's organized poorly IMO). Here is a good place to start if you want to set up a lab. There's not much in the way of official tutorials from MS so you'll want to check out blogs like windows-noob, Deployment Research and Deployment Bunny. There are also a few SCCM guys in the thread that can probably answer any questions. fake edit - also ConfigMgrDogs
|
|
#
?
Jul 23, 2015 16:19
|
|
|
Sacred Cow posted:Here is a good place to start if you want to set up a lab. There's not much in the way of official tutorials from MS so you'll want to check out blogs like windows-noob, Deployment Research and Deployment Bunny. There are also a few SCCM guys in the thread that can probably answer any questions. These are great, thanks!
|
|
#
?
Jul 23, 2015 17:06
|
|
|
This is the enterprise thread, but we prefer our bespoke artisanal enterprises, not fortune 500's. Internet Explorer posted:I still don't understand why you need login scripts using VBS. The whole world has moved passed login scripts.
|
|
#
?
Jul 23, 2015 17:21
|
|
|
Gerdalti posted:I want to learn SCCM (and later, SCOM). Where should I start? I don't seem to be able to focus on just browsing the info on Technet (it's organized poorly IMO). Along with the other good info above. Check out MyITForum.com specifically their SCCM Email list. Really great information goes through there and it's populated by a ton of SCCM MVPs. In general the SCM Community is massive and generally very helpful. The most important thing to know about SCCM is the speed at which is operates is inversely proportional to how much you want something to happen. Trying to push that critical 0 day patch to everyone in the company? It's going to take its sweet sweet time. Accidentally deploy Windows 7 image to all servers? Lightning fast! SCOM is a bit more difficult to find great info on. Lots of blog articles on specific stuff but no great centralized location for good info and the Community is pretty weak as it's largely corporate guys who do scom as a part of their normal job rather than being a specialty. Set it up, monitor some stuff, and fiddle with it until you "Get" how the classes, discoveries, monitors and such work then start doing some low level MP authoring to ensure your liver is properly damaged.
|
|
#
?
Jul 23, 2015 18:15
|
|
|
Zaepho posted:The most important thing to know about SCCM is the speed at which is operates is inversely proportional to how much you want something to happen. Trying to push that critical 0 day patch to everyone in the company? It's going to take its sweet sweet time. Accidentally deploy Windows 7 image to all servers? Lightning fast! Also, patching is just as much political as it is technical. Organizing Maintenance Windows for servers and scheduling reboots for workstations/laptops will always make someone at your company hate you. There's no way around it so just embrace it. I give users an 8 hour reboot window and still get complaints that I don't allow enough time.
|
|
#
?
Jul 23, 2015 18:49
|
|
|
Not sure where to ask this, but its in an windows enterprise environment. Does anyone know if you can send receive text or mms over avaya IP office without their little app messenger thing? could it be fowarded to email if sent to an ip phone #? will move/edit if shouldn't be here.
|
|
#
?
Jul 25, 2015 14:06
|
|
|
|
| # ? May 14, 2024 19:55 |
|
|
pretty sure you need the app
|
|
#
?
Jul 27, 2015 16:51
|
|