|
FISHMANPET posted:You've got a weird boner for PFEs let me tell you. Ugh. Your first two examples are that a specialist consultant is coming to your network to work through some of your problems. But they don't work for you, so they don't know your network like you do. You could spend a week gathering information before coming, a 'pre RAP' sort of engagement.. but Microsoft are pretty handy with the code so they just wrote a tool to do it. But you didn't run the tool, so a consultant comes to your network to work on your problems but you forced him to come in blind and just make it up as he went along. As for getting the tool to run, I've never had problems. I am also talking with the TAM and PFE via email leading up to the RAP, so if I had a problem I would have just emailed them and the PFE would have steered me in the right direction. So far, we've literally had 'my boss/organization can't follow through on simple responsibility' and 'running the tool was a technical challenge for us'. You're not off to a good start. Can you imagine being the PFE in this situation? Since you can buy a RAP as a service, just pony up some cash and MS will come and do it, they must run into this frequently. I have to go to some random corp and just be the all-knowing MS guy with no background and probably a hostile reception because these people work in such a shitshow that everything to them is a chore. So that's a professionalism/personal skills thing you need to have as a PFE before we've moved onto anything technical. FISHMANPET posted:But anyway, the survey is pretty dumb because (at leas the SCCM one) is about 3 questions about SCCM and 20-25 questions about the procedures in the environment. With a statement like that I'd usually ask next what is your background, because I've got some ideas based on what you said here. IT doesn't exist in a vacuum. It's presence in an organization is to meet business goals and the business either enables or hamstrings IT with how it's sees and implements it. In the modern world organizations that understand IT is a lot more about strategy and competitive advantage than keeping the lights on; thrive. It doesn't matter if you've installed hotfix XXX or your DNS is configured for scavenging or not if you're not backing up the directory. If you're backing up the directory, that doesn't matter if you're retaining those backups for longer than the tombstone period because your technical staff don't understand how AD works. None of that matters if you don't have a DR plan. Your DR plan, backups and the ability of your staff don't matter if you don't do test restores.. because you'll go to save the day with all that and instead pull your hair out. Microsoft has acknowledged this immutable bond between the business and the technology. The best techs in the world with the fastest servers and best software will still be restricted to mediocrity if the business doesn't acknowledge the assign resources to important aspects of the IT, which may not directly contribute to uptime today. This is where a RAP can help you as the tech, you've been saying to your boss for months that we really need to sit down and spend a chunk of time and write some proper DR stuff. He's not stupid, he's been saying the same to his bosses.. but it gets lost in the triage of management where your voice is one of hundreds all crowing about their area. Now however, the recommendation to do that DR work (or whatever, one of the many business aspects a RAP covers) isn't from you or even your boss, it's from Microsoft directly. Your org paid money for this engagement and managers usually have to come up with value for the money they've spent.. so it can be the difference between really pushing through the poo poo and approaching best practice or just running in circles for ever. If you'd already run through all this with a previous RAP and remediated it, then tick those questions as 'done' and move on. The point here is to make you go through the IT governance associated with not being a shitlord and really think about if you've got your bases covered. Does it sound like I'm talking down to you? I'm just explaining some of the principals I've learned in my experience. Unlike other areas of SA where your ability to pull out a snarky comment or hook into popular culture can validify your post, here we are talking about something real. There is going to be variation in the experience of the posters and not everyone is equal. When you say something like 'A RAP questionaire is silly because it's got a strong focus on process rather than technical details', I don't agree and have articulated why. FISHMANPET posted:So I finally get the tool to run, upload the data, and take a look at the results. First critical issue I decide to look at is related to MPKEYINFORMATION requests. It goes to a URL on each management point (http://mp) and checks the result. If it's a long string of characters it checks out, otherwise it fails. So it's critical. I go there, I get a 403. I look at the troubleshooting steps, very robust, but none of it fixes it. So I google MPKEYINFORMATION 403, and this is the first result: https://ramzibot.wordpress.com/2012/10/04/mpcert-mplist-access-denied-error-after-securing-the-management-point-by-a-certificate/ Well.. it's a script and often scripts do dumb things. You normally just roll on and ignore it, but if it was really holding me back I would have emailed the previously mentioned allocated MS resources and sorted it out.. not spend time sperging over Technet trying to 'fix' it. What I would have done is once I'd established these items were erroneous, I would have made notes to that effect and kept rolling. Then in my meetings I would explain this and be seen as having detailed insight into the network that even MS's tools didn't pick up.. which translates to you being good at what you do. It's an opportunity here.. not something to get frustrated and start searching job sites about. Based on the engagements you've had, you rate RAP engagements and PFEs as 'average at best'. But we've just seen how you never prepared and therefore executed an engagement in a professional way, but somehow Microsoft is to blame for this. I'm the last to say MS is perfect and I've got a career of dealing with their quirks. But I think you're off base here. Man, being MS is a hard gig (and therefore I respect the people that do it). Lastly, it's totally possible (even likely) there is little connection between the international arms of MS and MS in Aus and the UK is nothing like MS in the US. My experience is not American, so I may just be coming from a completely different place to you. You have to appreciate the irony if the reality is the US side of the business is letting the corporation down. Tony Montana fucked around with this message at 03:02 on Aug 1, 2015 |
# ? Aug 1, 2015 02:56 |
|
|
# ? May 28, 2024 16:09 |
|
Like I said you sound like a cool dude. I especially like how you trimmed out any parts that might implicate that Microsoft is not 100% impeccable. Anyway, I'll be contacting our TAM to get in contact with the PFE about the "critical" errors (which I have already noted as Not Applicable in the RAP). But because of the way this was just sort of dumped on me (and this is my environment's fault, not Microsoft's) I don't know who I have access to or what's in scope or out of scope. Anyway there's plenty of blame to go around between me and my enviroment, with Microsoft probably being in the minority. The PFEs I've worked with have been knowledgable but you're right, it's hard to come into a strange environment and be expected to answer questions about it. For what it's worth, we had some engagements with an SCCM PFE before I started here and my boss said he pretty much new more than the PFE. But he's also kind of a know-it-all too. Also as much of a pain in the rear end as Microsoft's documentation is, it's not like anybody's is any better. And there is plenty of actually useful feedback in the RAP tool, though it sounds like the AD one is better. It doesn't tell me how exactly it gathered a particular piece of data so I have to kind of work backwards from the scant information the tool gives me. I've got a friend that works at Microsoft (in development) and it's a big company. There's tons of little things that slip through the cracks because things are split between various teams and they don't interact the way they should etc etc. So it also wouldn't surprise me at all if the PFE programs in the USA are totally different than in other countries.
|
# ? Aug 1, 2015 07:07 |
|
This post makes me happy Microsoft is 100% impeccable? One of my very first IT jobs was fixing point-of-sale units in cafes (digging cables out from behind coffee machines, etc, haha) and these were the cash registers and ran Windows 98. loving 98, so the drat till would crash frequently and require restarts and staff would keep records on slips of paper until the PoS (it totally was a p.o.s) came back up. The AD tool was giving a description of the alert and then the powershell it ran to do the query for the domain to find it. I'll take some screenshots on Monday, it was really cool. It was doing some LDAP queries with some object properties I hadn't seen before and it taught me something. I'm sure US PFEs are just as competent as the rest, but as we keep trying to explain to management.. IT isn't actually magic. I'll bet if you give them the background they need and have asked for you'll get some real value out of their recommendations. It just teaches you a lot about the tech too, corners of AD and how they work that you pretty much never knew existed before a tool pointed it out and then a consultant explained the context to you. oh.. you keep the tool for 12 months. That's part of the RAP, you get the scoping tool or some variation of it for a year following the RAP. So you keep running it and working through the list (the thing generated months of work for me in a previous role) until you've got a clean dashboard and shiny best practice implementation
|
# ? Aug 1, 2015 08:49 |
|
I've got a branch office in Europe with 30 employees and I'm here for a week doing their IT poo poo. The entire organisation runs only Office 365 and Chrome. 25 employees are excited for an upgrade to Windows 10 right now but the leader of the 5 sales engineers says his people to remain on good old Windows 7 because they like to run vmware for demo environments to customers, and their worried that and other random utility apps they get in the field will have glitches. They already had a virus somehow take down the whole office a week back. I'm trying to tell them this is my one good opportunity while I'm in town to get all 30 people a consistent Windows image that I'll be able to better support and provide new features for, but it's a tough sell. I can tell the guy to eat poo poo and my way or the highway but I'd rather be diplomatic about it first. I could tell him we can hold off for six months and do it then, it's just a lot more work for me.
|
# ? Aug 4, 2015 08:22 |
|
Zero VGS posted:I'm trying to tell them this is my one good opportunity while I'm in town to get all 30 people a consistent Windows image that I'll be able to better support and provide new features for, but it's a tough sell. I can tell the guy to eat poo poo and my way or the highway but I'd rather be diplomatic about it first. I could tell him we can hold off for six months and do it then, it's just a lot more work for me. We are fighting this battle at our remote locations too. Generally they are fighting the corporate image because they've always has some leeway to install whatever they want and have things 'their way.' Since we were a Novell environment, we have literally never had any policy to the desktops aside from pushed applications from Zen. Now that people are receiving their Windows 8.1 machines with oodles of group policy, they are throwing a poo poo fit about not being able to change the desktop wall paper or play solitaire anymore. Just keep pushing that a standardized image helps to eliminate variability among machines, decreases deployment time in the case of a failed or compromised machine, and makes troubleshooting issues much easier and faster. It is very hard to argue with those points as a sane manager.
|
# ? Aug 4, 2015 13:35 |
|
Read through a little bit in the thread and didn't see this come up but a customer of mine just posed this question. Is there any way to push Windows 10 upgrades from a central source such as WSUS? He is trying to roll windows 10 out to a large portion of his production environment and doesn't want to walk around because reasons. I have dug around and am not really seeing any way that this is possible. Any insight?
|
# ? Aug 4, 2015 20:19 |
|
Jiimy posted:Read through a little bit in the thread and didn't see this come up but a customer of mine just posed this question. Windows 10 upgrade isn't meant for businesses. That'll be breaking his licensing.
|
# ? Aug 4, 2015 20:24 |
|
Zero VGS posted:I've got a branch office in Europe with 30 employees and I'm here for a week doing their IT poo poo. The entire organisation runs only Office 365 and Chrome. 25 employees are excited for an upgrade to Windows 10 right now but the leader of the 5 sales engineers says his people to remain on good old Windows 7 because they like to run vmware for demo environments to customers, and their worried that and other random utility apps they get in the field will have glitches. They already had a virus somehow take down the whole office a week back. I'm curious why you're trying to upgrade to literally a week-old OS for an entire corporate remote office that you're only at for a week. Are you sure your licensing even covers this? What about when they encounter bugs/problems?
|
# ? Aug 4, 2015 20:30 |
|
GreenNight posted:Windows 10 upgrade isn't meant for businesses. That'll be breaking his licensing. Not talking about the free stuff. He's in the process of getting his enterprise licensing but he's trying to figure out if there's a way to deploy windows 10 from a centralized location.,
|
# ? Aug 4, 2015 20:31 |
|
Jiimy posted:Not talking about the free stuff. He's in the process of getting his enterprise licensing but he's trying to figure out if there's a way to deploy windows 10 from a centralized location., Makes sense. None of the updated imaging tools are out yet for Windows 10.
|
# ? Aug 4, 2015 20:34 |
|
GreenNight posted:Makes sense. None of the updated imaging tools are out yet for Windows 10. Why they gonna do me like this!
|
# ? Aug 4, 2015 20:37 |
|
GreenNight posted:Makes sense. None of the updated imaging tools are out yet for Windows 10. I thought I saw an MDT release at a minimum. SCCM 2016 should be dropping pretty quickly. Last I heard the plan was within 90 days of the Windows 10 Launch. Edit: I'm terrible. It was the Preview of MDT that had windows to (LTI only) support.
|
# ? Aug 4, 2015 20:38 |
|
The Windows 10 ADK has been released, so now you can get a Windows 10 boot image into SCCM, but you have to do it manually and you can't modify the image from within the console. So I'm guessing there's gonna be a hotfix or CU for a 2 month old software release that's been on the roadmap for like a year. Good job Microsoft, really keeping your poo poo together there. And still now MDT release for Win 10. E: Hahahahaha, they've released CU1 for 2012 R2 SP1/2012 SP2 (which by the way means I'll be running SCCM 2012 R2 SP1 CU1 and that name alone makes me want to kill myself) and it doesn't add support for the Windows 10 ADK! Great job guys! FISHMANPET fucked around with this message at 20:58 on Aug 4, 2015 |
# ? Aug 4, 2015 20:38 |
|
FISHMANPET posted:The Windows 10 ADK has been released, so now you can get a Windows 10 boot image into SCCM, but you have to do it manually and you can't modify the image from within the console. So good. Thank u bill gates ur glory will shine into eternity with the angels.
|
# ? Aug 4, 2015 21:06 |
|
Our PFE and TAM are trying to convince us an in-place upgrade is the way to go for deploying 10. Sounds like a loving nightmare for testing app and driver compatibility. Thankfully no one is in a rush to upgrade so I'll just wait for the proper deployment tools thank you very much.
|
# ? Aug 4, 2015 21:07 |
|
Windows 10 just reeks of "we gotta shove this out the door in time for back to school" and it'd be funny if it wasn't also so sad and also if I wasn't sitting here in the trenches with people bugging me about deploying Windows 10.
|
# ? Aug 4, 2015 21:11 |
|
Jiimy posted:Read through a little bit in the thread and didn't see this come up but a customer of mine just posed this question. Can you get it in a .msu? Windows has a utility called wusa.exe that can run /quiet from a login script. SUS already catalogs updates for 10 so the official solution is probably coming very soon E: Keeping in mind, like the above reply says, 10 isn't finished yet. Check out the right click menus in edge or try to keep cortana working for more than an hour Roargasm fucked around with this message at 21:26 on Aug 4, 2015 |
# ? Aug 4, 2015 21:24 |
|
Jiimy posted:Why they gonna do me like this! I found this: http://blogs.technet.com/b/msdeployment/archive/2015/07/30/windows-10-adk-release-and-mdt-2013-update-1-plans.aspx SCCM 2012 R2 SP1 supports imaging Windows 10 along with in place upgrades.
|
# ? Aug 4, 2015 21:28 |
|
GreenNight posted:Windows 10 upgrade isn't meant for businesses. That'll be breaking his licensing. Source for this? The Win 10 free upgrade isn't meant for Windows 7/8 Enterprise Edition, but I'd like to see the fine print that says I can't upgrade computers with Win 8 Pro keys baked into the bios. CLAM DOWN posted:I'm curious why you're trying to upgrade to literally a week-old OS for an entire corporate remote office that you're only at for a week. Are you sure your licensing even covers this? What about when they encounter bugs/problems? Not even our lawyer can figure out what Microsoft's licensing covers, guess we'll see. I'm upgrading them because they're all going to have the same image on the same hardware. I've been testing the Windows 10 preview extensively at work so it's not a week old as far as I'd consider it. I have someone there who can clone new laptops and I can remote in to any of them. The big point of Windows 10 for me is we're not on a domain, but Azure AD Cloud Join gives us device management and single sign-on which we sorely need. The bugs/problems are going to be limited to global issues which I'll need to address for the whole enterprise anyway. Last but not least I won't make it back to this place for a while if ever, so if the upgrade has a time limit and I have to disrupt everyone to do it, might as well rip the bandaid off and get it over with. Zero VGS fucked around with this message at 01:02 on Aug 5, 2015 |
# ? Aug 5, 2015 00:46 |
|
Our make or break application won't be supported under 10 for 12 months. If you guys could sort out all the licensing and deployment stuff before then, I'd appreciate it.
|
# ? Aug 5, 2015 03:57 |
|
What kind of brain parasites do you have to have to think that autodeploying Windows 10 a week after release is good policy?
|
# ? Aug 5, 2015 17:03 |
|
OK, so SCCM 2012 R2 SP1 does in fact have full support for the Windows 10 ADK, you just need to reboot the Site Server to get it to fully register. The Config Manager team finally released a blog post detailing how the Windows 10 ADK and SP1 work together: http://blogs.technet.com/b/configmgrteam/archive/2015/08/05/windows-10-adk-and-configuration-manager.aspx Just updated my alphabet soup of a change request from "Install SCCM 2012 R2 SP1" to "Install SCCM 2012 R2 SP1, ADK for Windows 10, and SCCM 2012 R2 SP1 CU1"
|
# ? Aug 5, 2015 19:26 |
|
FISHMANPET posted:OK, so SCCM 2012 R2 SP1 does in fact have full support for the Windows 10 ADK, you just need to reboot the Site Server to get it to fully register. The Config Manager team finally released a blog post detailing how the Windows 10 ADK and SP1 work together: http://blogs.technet.com/b/configmgrteam/archive/2015/08/05/windows-10-adk-and-configuration-manager.aspx Yeah I updated my sccm install to 2012 R2 SP1 CU1, but I haven't found good step-by-step instructions to install Windows 10 ADK other than "uninstall 8.1 and install 10 then update other poo poo".
|
# ? Aug 5, 2015 19:30 |
|
I found this: http://blogs.technet.com/b/brandonlinton/archive/2015/07/30/windows-10-adk-boot-image-updates-for-configuration-manager.aspx That says you can install the ADK before the upgrade and if so everything will "just work." It also tells you how to import new boot images if you install the ADK after the SP1 upgrade. However the other link I posted says you can't install without 8.1 ADK installed, but I don't know if that's referring to R2 in general or SP1 specifically. On my test site I upgrade to SP1 then installed the ADK, when I do the upgrade on production this weekend I'm going to install the ADK first and see if the prereq checker likes it or not. E: It doesn't say it anywhere I've found but you'll have to manually create a USMT for Win 10 package. You can look at the Data Source for the USMT 8.1 package to see what it should be for 10. But oh yeah there's a bug in USMT 10 where it won't work when deploying Windows 7, but there's a workaround: http://deploymentresearch.com/Research/Post/497/Fix-for-Windows-7-deployments-failing-after-upgrading-to-Windows-ADK-10.
|
# ? Aug 5, 2015 19:47 |
|
God damnit what a pain in the rear end. I'll wait until CU2 I guess for those bugs and better documentation.
|
# ? Aug 5, 2015 19:50 |
|
RSAT not working on Win10 I take it? I installed it, but I don't see it in add\remove features.. or on the computer anywhere..
|
# ? Aug 5, 2015 20:45 |
|
FISHMANPET posted:Has anyone gone through a RAP assessment? My boss just dumped this on my lap and said "We're RAPing SCCM this year" and I just have to fill out this silly survey and click "go" on a program I install somewhere? Did a SQL server RAP a few years ago. Shits powerful, I wish they would release even a slightly neutered version of it to the public at large. I'd gleefully run a RAP on every server I have.
|
# ? Aug 5, 2015 20:47 |
|
lol internet. posted:RSAT not working on Win10 I take it? I installed it, but I don't see it in add\remove features.. or on the computer anywhere.. No. There was a beta RSAT for an earlier technical preview version, but no release yet. This is one of many reasons why it's bad to use a week old OS in an enterprise setting. CLAM DOWN fucked around with this message at 21:49 on Aug 5, 2015 |
# ? Aug 5, 2015 20:48 |
|
AlternateAccount posted:What kind of brain parasites do you have to have to think that autodeploying Windows 10 a week after release is good policy? Right? At this point I have a test laptop with it installed. That's it.
|
# ? Aug 5, 2015 21:04 |
|
At least the RSAT was expected, they've never had RSAT ready with the general release.
|
# ? Aug 5, 2015 21:19 |
|
AlternateAccount posted:What kind of brain parasites do you have to have to think that autodeploying Windows 10 a week after release is good policy? I'm manually deploying it by hand to each individual to make sure they're fine, I'm not doing an SCCM blast. I like face time and it's a good way to see who's been up to trouble. As of today I have a couple guys up on it, more to come tomorrow. I took my Windows 8.1 image and upgraded it, every application still has works perfectly as-is with no tweaks so that's what they'll get. I'm not saying Microsoft can do no wrong, but this time around they have an army of guinea pigs on the Insider track to test updates on before they push them through to the business branch. Laugh at me I guess if it all blows up but at this point I think the odds are the same as my users on Windows 7 getting hosed by something. I'm only at this location for a week, the upgrade is only good for a year and Microsoft I'd going to drag everyone living and screaming in the meanwhile. gently caress it, Yolo.
|
# ? Aug 6, 2015 01:04 |
|
#notenterpriseproblems
|
# ? Aug 6, 2015 02:41 |
|
CLAM DOWN posted:No. There was a beta RSAT for an earlier technical preview version, but no release yet. This is one of many reasons why it's bad to use a week old OS in an enterprise setting. What other reasons are there? Need to test it sooner or later anyways, and it's not that big of a deal that RSAT is not available for it as I can just remote in anyways to the DC. Aside from RSAT, there hasn't been much problems. Reality is worse comes to worse is it doesn't work and I convert back and have a couple hours downtime. lol internet. fucked around with this message at 14:25 on Aug 6, 2015 |
# ? Aug 6, 2015 14:20 |
|
I wouldn't push out Win 10 to my entire Enterprise (though I understand why Zero VGS is doing it, sometimes life gives you poo poo and you gotta make a poo poo sandwhich). But I don't see any problems with installing it on your work machine to test stuff out. I'll probably be doing that next Monday, since I'm upgrading my site on Saturday.
|
# ? Aug 6, 2015 17:12 |
|
lol internet. posted:What other reasons are there? Need to test it sooner or later anyways, and it's not that big of a deal that RSAT is not available for it as I can just remote in anyways to the DC. As this is the enterprise thread so we're talking enterprise and corporate environments, the reasons why you should not deploy a 1 week old OS to an enterprise are: -No security baselines (ie. CIS) -No GPO setup and testing -No training for support personnel -Many/various bugs/issues -No knowledge or testing of applications/software/3rd party stuff You absolutely cannot say there haven't been problems and that's a very naive statement. There absolutely have been problems, there will continue to be (it's a brand new Microsoft OS...), and just because it works on your home gaming PC doesn't mean it's a good idea and it's not a problem to push it to an enterprise. I mean, this is the same deal as when Windows 7 and 8 came out, etc, this isn't anything new or unknown, it would have been irresponsible to move to Windows 7 a week after release too
|
# ? Aug 6, 2015 17:22 |
|
With this thread covering enterprise topics, is it the de-facto destination for SCCM discussion? Everything I'm reading about application vs package deployment points to application catalog deployments lacking the ability to start installation upon winlogon -- as is possible in gpo or sccm package deployment. Being somewhat new to the sccm 2012 scene, I'm left scratching my head a little regarding precisely why.
|
# ? Aug 6, 2015 17:35 |
|
Fuuuuck me. I had to flatten a laptop running Win 7 home premium but it has office 2013. I was able to connect the hard drive to a different machine and run produkey on itcode:
|
# ? Aug 6, 2015 17:40 |
|
Potato Salad posted:With this thread covering enterprise topics, is it the de-facto destination for SCCM discussion? The application deployment evaluation cycle is what triggers application deployments and it runs on a different schedule without tying into winlogon (that doesn't answer the why part...Microsoft?). Unless you absolutely have to have it run at Winlogon, use an app. For your own sanity's sake and all that is frigging sacred.. USE APPS!! Unless you have a VERY compelling reason (reason.. not excuse) not to. I'm willing to bet it was a feature they felt was either unnecessary or they were unable to get it in before their deadlines (To ship is to Choose).
|
# ? Aug 6, 2015 17:42 |
|
mewse posted:Fuuuuck me. I had to flatten a laptop running Win 7 home premium but it has office 2013. I was able to connect the hard drive to a different machine and run produkey on it OEM license? Zaepho posted:The application deployment evaluation cycle is what triggers application deployments and it runs on a different schedule without tying into winlogon (that doesn't answer the why part...Microsoft?). Unless you absolutely have to have it run at Winlogon, use an app. For your own sanity's sake and all that is frigging sacred.. USE APPS!! Unless you have a VERY compelling reason (reason.. not excuse) not to. I get the eval cycle logic -- "Should I install/uninstall this package? Is this the user's primary device?" What I've been reading is that, with application deployment lacking the capacity to restrict initiation of installation to an environment guaranteeing no browsers are open for, say, a Flash deployment, we're left to our own devices on managing communication of change management with the users. The same small (to continue the example, Flash) package install that we could get away with sneaking under a user's nose unobtrusively upon login with an sms / sccm'07 package is going to require us to pop a window up asking that the user close browsers, defer x number of times, yadda yadda. That's fine and dandy for the big rare updates like going from Office 2010 to 2013, but for more frequent and small updates like Reader or Flash, it might get old. Along the lines of interacting with the user (close browsers or applications, defer installation, etc), PowerShell App Deployment Toolkit is looking really, really cool. http://psappdeploytoolkit.com/ Potato Salad fucked around with this message at 17:57 on Aug 6, 2015 |
# ? Aug 6, 2015 17:43 |
|
|
# ? May 28, 2024 16:09 |
|
Potato Salad posted:OEM license? I'm not sure, you can get pro plus as OEM?
|
# ? Aug 6, 2015 17:47 |