back

Windows 10 (MD-100) (In Production)

Configuring Modern Desktops12 H 5 M

Episodes
Episodes
  • Deploy Windows
    • Configure Language Packs
    • Migrate User Data
    • Migrate User Data Part 2
    • Perform a Clean Installation
    • Perform an in-place Upgrade
    • Windows Editions and Activation
    • Post-Installation Configuration
  • Manage Devices and Data
    • Manage Devices
    • Manage Local Users and Groups
    • Configure NTFS Permissions
    • Configure NTFS Permissions Part 2
    • Configure Shared Permissions
    • Configure Shared Permissions Part 2
    • Configure Devices Using Local Policies
    • Configure Devices Using Local Policies Pt.2
    • Manage Windows Security
    • Manage Windows Security Part 2
    • Manage Windows Security Part 3
    • Manage Windows Security Part 4
  • Configure Connectivity
    • Configure Networking
    • Configure Networking Part 2
    • Configure Networking Part 3
    • Configure Remote Connectivity
    • Configure Remote Connectivity Part 2
    • Configure Remote Connectivity Part 3
  • Maintain Windows

    Configure Language Packs

    29 M

    • Episode Description
    • Transcript

    In this episode, Aubri and Mike discuss configuring language packs. They look at how to obtain language packs and talk about the different formats available. Then they install an additional language on a Windows 10 machine.

    Welcome to ITProTV. I'm your host Don Pezet. [CROSSTALK] [MUSIC] >> You're watching ITProTV. >> Hello and welcome to another exciting episode here at ITProTV. I'm your host Aubri Spurgin, and this is Windows 10. We are preparing for that MD-100 exam, and in this episode we are going to configure language packs. And the fellow who's gonna bring us all the information we need to know is Senor Mike Rodrick. >> Hola Aubri. How are you doing? [LAUGH] >> I'm doing great. How are you? >> I'm doing fine. Thanks for having me. Excited as always to be here. And yeah, we're gonna just kind of work our way down through this list of objectives as we're preparing for that MD-100. And one of the first ones in the list is installing language packs or configuring language packs as I like to say. >> Yes, right. >> That's a good place to start, right. >> Cool. >> And are pretty straight forward. Well you know when we think about language packs, obviously when we install Windows we have to pick at least one language, right, so that we can use our operating system. Usually the ISO that you're using is localized to you, like here my ENUS is gonna be installed automatically for me. I can detect that if I have Internet access, it can detect my region. If I have a multi-language ISO, again, it can try to detect what language. Or it'll ask me to pick, and you pick one. But after the fact, you might want to install additional languages. Could be that you need to add additional languages to your image to support multinational offices. Or maybe you're user or users work in multiple languages, so they need to be able to switch back and forth. Whatever the case may be, we need to be able to add more than that one that came with our Windows install. And that's the goal today is how do we do that? And let's start with just some basic info that they might get you with on the exam, and then we'll take a look at how we can actually accomplish this. We can add language and regional support to Windows 10 and Windows Server except for Windows Home, Home Single Language, and Home Country Specific. Which makes sense, right. If you have, we probably won't be dealing with that in our Enterprise environment, we're not gonna have the Home version of the operating system. But maybe you're supporting end users, maybe your job deals with selling PCs or supporting home users, or something like that. Understand that if you have a home single language, you can't add additional languages, which is kind of why they call it a single language, right. >> Right, makes sense. >> Yeah, I mean if you want to point it out, but once you hear it, you're like, duh, that makes sense, yeah. Also home country specific, you wouldn't be able to add additional language packs to it because, again, it's country specific. It's not meant to go anywhere else, be used anywhere else. But doubtful, I've never seen those editions, any home single language or home country specific, but they're out there and if you're dealing with one, understand that you can add a language back. >> Some countries deal with more than one language. >> They do. >> So how does that work out? >> That means you would not want to use that ISO to install Windows. >> Okay. >> Yeah. >> All right. >> You'd wanna buy a multi-language version of Windows or something else. >> Okay. >> Yep, for sure, for sure. All right, so we can't add it, except for those two. Again, they have at least one language pack, and there's language components. Now when we go to add our language packs, we can actually do what they call localization packages for Windows. And they used to be, and I say used to be because it is changing as we move through our newer versions of Windows 10. It used to be .cab files, dot C-A-B or short for cabinet file, which is very similar to a compressed file, like a WinZip file or something like that. The hierarchy of files in there. And it will include the UI elements, my user elements. That means the dialogue for text boxes, like when you see a message that says, do you want to continue, yes or no? I need that to be in a particular language, and I need the yes or no to be in the right language. So text for dialogue boxes, menu items, help files would also be updated assuming we get the appropriate language pack. And let's go out to my screen here, I've got the Microsoft page pulled up. You guys can go docs.microsoft.com. I'll throw this in the show notes for you because I did wanna point out a couple of things. As, again, Windows 10, changing so fast and that's what our exam is on, so we do need to be familiar with this. But when we look at language packs, they can still be CAB files. Even with Windows 10, we can still get these from Multi-language Pack ISO, from Microsoft, delivered as a CAB file. For example, they give you the example here of Microsoft Windows client language pack ESES, so that'd be Spanish from Spain I believe, .cab. There's also these, and let me zoom in if you can see that a little bit, I know that's a little small there. There are language interface packs, or LIPs as they like to call them. These are partially localized language packs, and they require a base language. For the exam that's really what I want you to understand, is that a LIP is a language interface pack and it's partially localized, meaning, I think the example they use here is French. So they've got this AMET, let's see if I can figure out what that one is. It would need a base language, so it might be a regional version of French. I think one of the examples they use in this documentation is Luxembourtgish, I'm not exactly sure what that is. But it requires that you already have the French language pack installed because it's not an entire language pack, it's just a few regional dialect type things, all right. We also have features on demand which gives me the ability to not install all the components in the beginning, save a little space maybe on my image and then if the user needs them they can install them. And we also have to worry about recovery languages possibly, right. You might wanna update the user interface for the Win PE environment. And not all language packs contain all these components. You might find some that just do the Windows dialog boxes and the help for handwriting. But they don't have text to speech support and things like that. Others are fully fledged out, are fleshed out and they have all of the different components. So you do have to pay attention to that. Do I need optical character recognition? Some of the language packs, especially some of the regionalized versions don't include that, all right. The base language pack might, but the regional pack might not. So you do have to pay attention to that. Now where we get these language packs can also be a challenge if you're trying to study, as you're practicing or testing this out. It was difficult for me, I know. You have to either go out to Microsoft's OEM site or Device Partner Center. So you need a volume license or you need to be an OEM that has access to this. If you're an IT professional, you can go out to your volume licensing site. If you're a builder or an OEM, you can go to the device partner or Microsoft's OEM site and get them from there. Either one of those locations will allow you to download the appropriate, either the pack itself or maybe an ISO that contains multiple packs in it. The other thing that you have to pay attention to, and I'll tell you this is probably one of the most frustrating parts about supporting Windows 10 currently, is the versioning and how fast they're changing. The language pack has to match the ISO or the version of Windows that you have installed. So if you have the language pack from 1709, but you're rolling out 1809 or 1803, it's not gonna work, all right. It will detect a version mismatch, and you're gonna have to go and get the appropriate one. So keep that in mind, you really have to pay attention to the build numbers and make sure that those hacks match or those versions match, right. All right, lets see, I believe that's probably enough. Again, I'll throw the link to this particular webpage in there so that you can go and do a little bit of research. Understanding just the basics of how languages are handled in Windows, and then knowing how to add them is really the key for this exam. And when we go to add our language packs, we have to decide, are we adding it into an online image or an offline image, right? If I've got, maybe Aubri comes to me and says, hey, I'm gonna be doing some work with our customers out in France. And I need French on my computer. I could add French to your computer, it'll be online, where you're just adding it to an existing install, or if we're opening up an office in France, and I need to deploy ten new laptops that all have English and French installed on them. Then I can do it, I can inject the language pack into our image, right? I can use a default WIM file, or I can create my own WIM file. And there's other ways, you can get into System Center and things like that, and handle this as well, but again, for this particular exam, it's really just looking at it from that client perspective. >> You know, that actually reminds me of when I use my Google Translate app, when I'm here in America and I'm just kind of looking up a word, I will have it online, but if I go to the country. I like to download it, in case I don't have Wi-Fi or data. And now I have this plethora of words in French, let's say. And it's really fun and great. It reminded me of this. >> Very good. Very similar in concept. I like it. All right. So, what do you say, we actually install some language packs? >> That would be amazing. >> All right, let's do it. Let's see, I think we've already got my screen pulled up here. I'm gonna jump over to a Windows 10 virtual machine, and what we're gonna do, if you're gonna add this, we're gonna do the offline first. Which means, we're gonna use tool like DISM, which is what I'm gonna use, there are other ways you can go about this. To mount up a WIM file, right, what we use to install our Windows image file. And we're gonna inject our language packs into that offline image. Then when we will deploy the image, the language is already there. They log in for the first time. They could go in their settings, and language, and they can choose to pick the appropriate language. So for that, there's a couple of things we're gonna do. I have got us ahead of the game a little bit. On my D drive of this Windows 10 machine, I have the Windows 10 Install.wim, already copied from the DVD over to my local hard drive. I'm gonna fire up PowerShell as an administrator, if it'll let me. There we go. We'll say yes to the good old UAC. And what I want to do is I want to mount that wim file. So that's gonna be dism/mount-image space / image file. I have trouble typing and talking at the same time. Colon. And then, I'm gonna cheat. I'll show you a little trick that I like to do. I love to use Windows and tab auto fill, especially for Windows pads. So I'm gonna hit a space, and then D:\, and where did I put the wim file? I put it in a folder called wim\win10eval, and then it's called install.wim. But once I've finished with that path, and taken advantage of the tab autofill, I need to get rid of that space. So see how I did that? Again, just a little cheat. You might or might not find that useful. /index:1 cuz remember, within a wim file, you can have multiple images, right? I wanna tell it which image I want to mount up, that I'm working with. And in my case, that's index number one/mountdir, or mount directory:D:\mount, and then I hit enter. And then we give this a minute, it's going to mount up the ISO, and when we come back, I will continue on. All right, that only took a couple of minutes, and the image has mounted up, so let's take a look at my screen here. We can see the operation completed successfully. So now we've mounted up that WIM file, so that we can manipulate it, and work with it. The next thing I wanna do is just run a little command to verify what packages currently exist in that WIM, so that we can prove that this working. And for that, it's just DISM/Image:, and then were did you mount the image? Well, remember, we used D:\mount. That's our virtual directory, or my pointer to that mounted image, so D:\mount and then space, /getdash, oops if I can spell that, Packages, and we hit Enter. And what it's gonna do is, it's gonna rifle through that image that's mounted up, and it'll list all of the packages. These are additional things that are installed in this particular version of Windows. And you'll see a lot of interesting things, like Windows Security SSP, and let me zoom in for you a little bit here. Prerelease client package, what else? Here's some language features, but you can see these are en us, en us, right? Because this is localized to me, this is the ISO I'd use here. What else, en us, language features, there's my handwriting. Notice that is also en us. And I think, there's my client language pack, and that is en-US. >> Can you make it a little bit bigger? >> I can, I'll zoom in just a little bit there. So there's my LanguagePack. I can also see things like, there's my LanguageFeatures-Handwriting, LanguageFeatures-Basic. So they'll do some of that OCR, the character recognition. And remember when I was talking about versions? You look at this number right here. That is what needs to match, when you talk about your installed version of Windows, or the Wim you're working with, and the language pack that you're getting. So I need to find a package that's 10.0.10586. And I can tell you, when I was setting up for this, that version is actually like one of the second or third releases of Windows 10, in 2015. So finding the right language pack and ISO for that was challenging, to say the least. All right. But, we've got it. So again, that was just a look to see what packages are currently installed. Notice there weren't any, or what did you say we wanted to do? What language you wanna install? >> We doing Spanish. Right. >> Spanish. Okay. We can do Spanish. Alright, so I have downloaded the ISO from Microsoft on our volume license site, and you can see the title up here, it's hard to read it LPLIPMULFRELELIP. That's just their language packs and lips, right, LIPS, Multi-user language, I think, is what that stands for. But anyway, that's not important. Inside x64, there's a folder called Language Packs. And inside there, are all of my different language packs. >> Right? And I think we'll just install them all. We don't wanna make the image any bigger than necessary. That's why we have these as separate files, and are not installed by default. >> How do you know which is which? Do you just have to kinda figure it out- >> You have to figure it out. >> Or does it say, is it, really, okay. >> Yeah, you have to kinda figure it out. >> For the most part it's easy, but some of them I have no idea. [LAUGH] >> Yes, from here, now if you go, and I'm gonna show you. To do it on a online version, it's a little bit easier to figure out what is what. But if you're using the ISO, yeah, you just have to know. >> Okay. >> All right, I'm sure there's a list of them somewhere, if we fired up being, we could probably find that. All right, but now that we've got that ISO mounted up, our next command is going to be to take one of those language packs, and then inject it into our image. For that again, we'll use dysim. Let me clear my screen, so I can get back to the top of the window there, and we're going to type in, dism /image:, and I've got to tell it what image am I working with. I might have more than one image mounted up. So just, d:\mount. Oops, and I can't type evidently, and my hand was not on the home row there, d:\mount/add-package/packagepath, and then the location. Now you could have copied those files off the ISO to a local folder. I could on the machine I'm working with I could have put them up in a network share. I just mounted up the ISO and I'm gonna do it from there. The package path colon, I'm sorry, it's not a colon. This one is actually an equals and then, I'm gonna again cheat, e colon, backslash. What is that, it's in the folder called x64, and it's not gonna let me to my tab autofill anyway. So e:\x64\langpacks\user is Spanish we're gonna go es-es\lp.cab, and I'll end my quote, and I'll hit. Make sure that is in the right path. I wanna verify that I've typed in that path correctly. So there's my es es, there's the lp inside there. We look at that path, e:\x64\langpacks\es-es and then lp.exe. So we should be good to go. >> All right. >> I'll hit Enter. And this'll take it a minute because it's going to inject that into our image. You can see the progress bar has started. And if you get to this point, you're pretty sure you did it correctly as long as you picked the right package. If it was gonna fail because of version numbers or anything like that, we would have seen that already. So we'll let this run and when it finishes, we will come back and we see what we got. All right, that took maybe five minutes on my machine. It'll depend on your hardware. It has finished so let's jump back on my screen and see what we've got. Really, you're not gonna see much. I can see that the operation completed successfully. And how I would verify if I wasn't sure, or if I wanted to just prove to myself, we could do another. In fact, I'll just use my up arrow here. I'll run that same command dism, image colon, and then the path to the mounted image and then forward slash get packages. We'll hit enter, let that run for a minute. See if I can maximize that, there we go. And what we should see, and I'll zoom in here in just second, as soon as I find a couple. If I scroll back up through this list, here I can see, Right, yes, yes, right? >> There's my language pack, if I go down a little bit further, let's see if we can see any additional ones. Some of these might have rolled. Sorry, it's really hard to move around when I'm zoomed in. So let me zoom out and I can zoom back in for you in just a second. There's another one, there's es es. And that's my pre-released client package. And it looks like that's about all I got for that one. But again, we can see that those packages were indeed added to that image. And now when I deploy that image, it'll already be there. So if somebody wants to switch to that particular language, they can go into their settings and they can pick from a drop down list, it should show up, all right? Now, in order to finish this process, if this was real world and I wanted to use this wim, I would need to unmount and commit the changes to that wim file. Remember, when you mount a wim file, you've got it loaded up and you're making changes to it, you can always quit and discard all your changes. Or you can choose to commit and actually write those changes back into the wim file as it packages it back up, and closes it, and writes it back to disk. So it's an easy step to forget and you can lose all your changes. We're not gonna wait for it to finish, I don't wanna actually sit here and wait for it. But what you would do, it would just be dism/, and you can do the commit as a separate command or you can do it when you unmount the image. If you wanna do it as a separate command, dism /commit-image /mount dir:d:\ mount, all right. So if we zoom in there you can see basically dism /commit-image and then the path to the directory where we have mounted up that particular image. I'll zoom back out. That would commit it but it wouldn't unmount the image, right? I could still go back and make additional changes to it, or whatever I needed to do. If I knew I was done, I could also commit the changes, and unmount it at the same time. That particular command is gonna be something like dism /unmount-image /mountdir:d:\mount >> That says counter instead of mount. >> What's that? I did, didn't I, oops, thank you, all right? So almost the same command here, we're just specifying unmount-image instead of commit-image, and we would add a /commit to commit those changes and unmount at the same time, or What do you think that would do? >> Get rid of it, [CROSSTALK] [LAUGH] >> It would get rid of my changes, right? It would throw all the changes away. Maybe I added the wrong language, and was shucks, that was the wrong one. I can go ahead and discard and unmount, all right? Now, I'm not going to, just because we wanna finish up this demonstration. [LAUGH] Do keep in mind, though, I will have to go back and unmount that image, otherwise it remains mounted up. So don't forget to unmount the image when you're done, either discard or commit your changes. One other command I do wanna show you while we're in here is what if I wanted to use dism for an online image, right? I can do dism /online /add-package /packagepath: and then, in my case it's on the DVD still, so e:\x64\langpacks\es-es.lp or something like that. And this switch here, online, says hey, this isn't a mounted wim file, this is the current running machine that I want to inject the package to. So, with an online image, when you're sitting at the particular laptop, you can use dism to do it this way, or you can go into your settings and you can add them that way. If you had already downloaded or had access to the language pack ISO, this might be the easiest way to do it, all right? But I'm not gonna do that, either. We are gonna close PowerShell. And the other way you do it in an online image is just use your settings. On Windows 10, I can go to my Settings from my Start menu. And then we can go into Time and Language. And then Language over there on the left hand side. And we'll maximize that for a second. And here I can see what my current Windows display language is. If I hit the drop down list, you'll notice I have nothing available in that drop down list. Because remember, by default, Windows just installs the one language pack, all right? There's add a Windows display language with Local Experience Packs. Below that I have Add Languages, in here I can see the current language. And then there's all these little icons, all right? And these are important. Because as you're browsing through the different language packs it, depending on what you want, might help you determine which pack to get. Some of them don't include all of the components, all right? This one, the first one there is the display language, the interface, things like that. The second one is text-to-speech. Does that particular language pack support text-to-speech? Does it support speech recognition, handwriting, as well as typing, all right? So I'm gonna zoom back out. This would take you to a little article about how to add language packs. We're just gonna click Add a Language. Now you do need to have Internet access. This is gonna reach out to Windows update and pull the files from there, right? Remember I was saying that as an IT professional, if we wanna do this to the image, we need that language ISO. You can do it with a reference image as well. You could give it Internet access and download the language pack that way in a reference image. What did you want to do for this one, Aubri? >> Russian. >> All right, let's see if we can find some Russian in here. We'll try their search, sometimes that works, sometimes it doesn't. Here I can see Russian. >> Ruski. >> And if I zoom in a little bit, you'll see that this is one of those languages that doesn't have all of the features, right? I don't see, what was that one? The dictation, right? The speech recognition. I do see text-to-speech, handwriting and display language, right? Some of these other ones, you notice, don't have, I don't know what you're gonna get with that because it doesn't look like much, right? [LAUGH] We're gonna select this one, though. I'm gonna zoom back out so we can see. And I will click, there's a nice little chart down here to tell you what the different ones are. I'll click next. And then because this one included multiple components, I might not want all of them, right? Handwriting and speech recognition, those take up a little bit of space when we install them. And maybe I don't need those features, I just want the basic typing, or I just want the language itself so that I can see Windows in Russian. And I don't need speech, and I don't need handwriting, right? I can save a little space. Now granted, nowadays, 12 megabytes doesn't seem like much, right? >> No. [LAUGH] >> Not with today's hard drives. But I do wanna point that out, you can pick and choose the different components that you want. All right, we'll go ahead and choose install. And we'll let that reach out, and it's gonna again pull from Windows Updates. We'll let this go for a minute, and when we come back, we'll take a look at our results. All right, so that didn't take too terribly long, let's take a look at what we have now. And what I wanted to show you before I do this was, will be displayed. Let me zoom in for you. Will be display language after next sign in. So you can see my drop down list has changed to Russian. Right now I have two languages in my drop down list, if you can see that there, right? And I'm gonna go ahead and sign out. And I'm gonna have to close my VM connection, because I've had a couple of issues with the resizing and the scaling. So once I've logged out, I'll log back in. Get that go full screen again. Log in as my user account. Oops. And let's see what we've got. Hopefully, well, I don't know, I won't be able to read anything, but we should see that it is Russian. Pretty obvious, right? In fact, I can just look at my desktop here, if I could zoom in. Zoom in not playing along. Zoom it has locked up on me. I get some. I don't know if you can see this down in the bottom corner, thank you, Titus. >> Cool. >> If I can get, there you go zoom it, it's starting to work now. All right, there you can see that even the warning about this not being active. Can you read that? >> I can. I don't know what it means, but [FOREIGN] Windows 10 [FOREIGN], okay. >> [LAUGH] Wow. >> You know, other stuff, I can read it, but I felt the pressure, so yeah. [LAUGH] >> Okay, well that was pretty impressive to me actually. But yeah, we can definitely see that Russian is now my display language. That's the little warning that you get telling me that I need to license my copy of Windows, I've got like 83 days left. If I go down here to my actions pane, you'll see the system is definitely switched over to Russian, right? If I zoom back out and I open up, I don't know, Windows Explorer, for example. There we go, we see more Russian. >> Yeah. >> All right, so the moral of the story is we can add additional languages to Windows. We can change the display languages, it just depends how we wanna go about it. If we're doing an offline image, we're gonna go and get those language packs as an OEM or a system builder. I can get those from Microsoft, as an IT pro, I'll get it from my volume licensing center. Or if I'm just an end user, I can simply open up my online image. I can go into my settings and I can go to Language, and I can pick a language and it will reach out to Windows Update and pull that language down and allow me to use additional languages. So there you go, working with language packs in Windows 10. >> All right, this has been configure it language packs in Windows 10. So thank you so much, Mike, for guiding us through that. Very neath stuff, I love learning how to mix and match the language on my computer or on my phone. So thank you all out there for watching, adios and [FOREIGN] from ITPro.TV. I have been your host Aubri Spurgin. >> And I'm Mike Rodrick. >> And we'll see you next time. [MUSIC] >> Thank you for watching ITPro.TV

    Just you? Training a whole team? There's an ITProTV plan that fits.

    With more than 4,000 hours of engaging video training for IT professionals, you'll find the courses you and your team need to stay current and get the latest certifications.