Dec 14, 2018 - Hai sahabat! Biasanya, untuk dapat masuk atau mendaftar ke suatu universitas, ada beberapa jalur yang dapat ditempuh, seperti jalur.
If you require any more information or have any questions about our site's disclaimer, please feel free to contact us by email at. Disclaimers for www.soalut.com: All the information on this website is published in good faith and for general information purpose only.
Www.soalut.com does not make any warranties about the completeness, reliability and accuracy of this information. Any action you take upon the information you find on this website (www.soalut.com), is strictly at your own risk. Www.soalut.com will not be liable for any losses and/or damages in connection with the use of our website. From our website, you can visit other websites by following hyperlinks to such external sites.
While we strive to provide only quality links to useful and ethical websites, we have no control over the content and nature of these sites. These links to other websites do not imply a recommendation for all the content found on these sites.
Site owners and content may change without notice and may occur before we have the opportunity to remove a link which may have gone 'bad'. Please be also aware that when you leave our website, other sites may have different privacy policies and terms which are beyond our control. Please be sure to check the Privacy Policies of these sites as well as their 'Terms of Service' before engaging in any business or uploading any information. Consent By using our website, you hereby consent to our disclaimer and agree to its terms. Update This site disclaimer was last updated on: Wednesday, May 23rd, 2018 Should we update, amend or make any changes to this document, those changes will be prominently posted here.
The watchdog inspects the Big Four and other firms annually by taking a random sample of audits and checking them for deficiencies and conflicts of interest. KPMG says that its new employee received a heads up from someone who still worked at the PCAOB about which audits would be inspected. The new employee then shared the information around. Eventually, five partners, including the head of the US audit practice, “either had improper advance warnings” or were aware that others had received this information and “failed to properly report the situation in a timely manner”, the firm said. All six people have been fired. Tampering with a random sampling process strikes at the heart of how auditors do their jobs. It is physically impossible for an accounting firm to examine and verify everything a big company does in time to provide investors with meaningful quarterly results.
The auditors have to select a relatively small group of transactions, investigate them thoroughly, and hope that they are representative of the larger company. The process can easily break down, as it did in the 2003 Royal Ahold accounting scandal, where employees at its US Foodservice subsidiary conspired with suppliers to lie to the auditors about whether specific transactions took place as described. That reality makes it all the more staggering that five KPMG partners failed to act on the danger posed by their secret tipster. Even schoolchildren know that it is cheating to get an advance copy of the test.
On the upside, when someone at KPMG eventually did the right thing and reported the shenanigans, upper level management reacted immediately and appropriately. That should send the message to the global firm’s 189,000 professionals in 152 countries that KPMG’s 51-page code of conduct really means it when it says “Your voice counts. So speak up if something doesn’t seem right.” The PCAOB also investigated and an employee has left as a result. “The improper disclosure here was clearly a violation of our ethics code and does not reflect the integrity and honour that the majority of PCAOB employees bring to their jobs every day,” says chairman James Doty. “I want to take a hard look at what additional safeguards may be necessary to reinforce the integrity of our regulatory processes.” Both reactions contrast pleasantly with the behaviour of Barclays chief Jes Staley, who this week was reprimanded for trying to unmask the author of a letter that his compliance department had classed as whistleblowing.
But the episode highlights the troubling side of Washington’s revolving door. While the US has long been comfortable with watchdogs and industry lawyers changing places, the auditing profession has a particular problem. The Big Four are so dominant that today’s regulator is not just a potential future industry peer, but literally tomorrow’s co-worker or boss.
Stricter conflict of interest rules and longer cooling off periods should be required. 51-page code of conduct Barclays reprimanded. Have a drive test first hand to our flip book of “ Directory of Coal Business in Indonesia, July 2017” on this link: This e-book is accessible with Windows-based computers. This flip book is created with Adobe Flash technology. These directories are available on an individual basis or embedded inside the research report on: Coal Business in Indonesia by Sando Sasako Jakarta, 20 July 2016 Last update: Jakarta, 12 April 2017 li + 479 pages, comprising of 214 tables and 98 charts You may experience the flip book version on Download the “Directory of Indonesian Mining Companies” into your android phones Here is the snapshot of the flip book of “ Directory of Mining Companies in Indonesia: Status of Clean and Clear, September 2016” version.
Directory of Mining Companies in Indonesia: Status of Clean and Clear, April 2017 How to order:. Kindly send your purchase order by SMS/texting to +62 851 0518 7118, +62 852 103 56 516 by mentioning your name, email, and mobile phone number. Upon receiving your order, we shall notify you our bank account number and the name of the account holder. Please notify us regarding your successful payment to our mobile number above. Upon effectiveness of the fund received in our bank, we shall email the link to download the ebook you have ordered and paid. The link to download shall expire in 24 hours. Have a drive test first hand to our flip book of “April 2017” edition on this link: Should you have any inquiries or questions regarding our presentation intention or elses, please contact us on +62 851 0518 7118, +62 888 1617 440, +62 852 103 56516 Direktori Perusahaan Tambang di Indonesia: Status Clean and Clear, April 2017 Direktori ini mencakup daftar perusahaan tambang seluruh pengumuman CNC, dari yang pertama sampai yang ke-24.
Cara pemesanan:. Silahkan order buku elektronik ini melalui SMS ke +62 851 0518 7118 atau +62 852 103 56516 dengan menyebut nama, email, nomor identitas (KTP dan NPWP), dan nomor telpon yang bisa dihubungi. Setelah order pemesanan diterima, kami akan mengirimkan nomor dan nama pemilik rekening. Harap memberikan konfirmasi terhadap pembayaran melalui transfer bank.
Setelah dana tercatat efektif di rekening bank kami, kami akan memberikan email berisi link untuk men-download buku elektronik yang telah dipesan. Link untuk men-download akan expire dalam waktu 24 jam. Terima kasih.
Materi yang terdapat dalam buku Direktori Perusahaan Tambang di Indonesia: Status Clean and Clear adalah sebagai berikut: Nama Pemegang IUP: Status CNC Pemegang IUP:, pengumuman ke SK Pencabutan No. SK No., Tanggal Luas konsesi (HA) ha, penambangan, tahap KEGIATAN Lokasi: Wilayah: Berakhir: Referensi provinsi SK No. Remark: Keterangan: Other contents available upon request are as follows: 1. Corporate Identification Number (Single ID Number) 2.
Addresses of Headquarter, Operational Office, Working Area 3. Telephone and fax numbers 4. Contact person 5. Mining license permits: History, Prevailing, Existing, Expired, Clean and Clear Status 6. Mining info: ownership, mined minerals and resources, concession area, current activities 7. Economic data: production, sales, investment, paid taxes and non-taxes to governments, manpower, services and expertise, infrastructure, reclamation plan and deposited fund.
Baso Patetengi A. Muhammad Yusuf,S.Sos. Rasyid Aal Rizki Tadang Palie, PT Aan Sukayat Aang Harto Abachus Niaga Jaya, PT Abacus Minerals Harvester, PT Abacus Multi Mineral, PT Abadi Buana Lestari, PT Abadi Jaya Indah, PT Abadi Ogan Cemerlang, PT Abadi Tarigan Abadi, PT Abadil Jayatama Sakti, PT Abalong Bombana, PT Abdi Bersaudara, CV Abdi Guna Bahari, PT Abdi Negara Buana Raya, PT Abdi Pertiwi Loka, PT Abdul Aruan Abdul Fatah. Sdr Abdul Gafar Lubis, Sdr Abdul Ghofur, Sdr H. Abdul Jawat Nasution Abdul Rahman Abdul Wahid, Sdr Abdularuan Abdulrahman.
P., Sdr Abe Jaya Perkasa, CV Abelindo Land, CV Aberta Wigadijaya, PT Abhimata Anugrah Abadi, PT Abisha Bumi Persada, PT Abrar Nusantara, PT Abu Salim Abud Suciptra, Sdr Abunain Aceh Kencana Mandiri, PT Aceh Mineral Gemilang, PT Aceh Mining Lestari, PT Aceh Poe Atra, CV Aceh Tuan Sinawari, PT Aceh Tuwan Sinarawi, PT Achiyat Ilyas Achmad Anwar, Sdr Achmad Buaethy Achyar, H. Acmad Fadly,Ft, H. % whois.apnic.net% Whois data copyright terms% Information related to ‘103.77.226.0 – 103.77.227.255’ inetnum: 103.77.226.0 – 103.77.227.255 netname: IDNIC-UPNSBY-ID descr: UPN Veteran Surabaya descr: Universitas Pembangunan Nasional Veteran Surabaya descr: University / Direct member IDNIC descr: Jl. Raya Rungkut Madya no 1 descr: Gunung Anyar, Surabaya descr: Jawa Timur 60294 admin-c: AF312-AP tech-c: AF312-AP country: ID mnt-by: MNT-APJII-ID mnt-irt: IRT-UPNSBY-ID mnt-routes: MAINT-ID-UPNSBY status: ASSIGNED PORTABLE changed: 20161026 source: APNIC irt: IRT-UPNSBY-ID address: Universitas Pembangunan Nasional Veteran Surabaya address: Jl.
Raya Rungkut Madya no 1 address: Gunung Anyar, Surabaya address: Jawa Timur 60294 e-mail: e-mail: abuse-mailbox: abuse-mailbox: admin-c: AF312-AP tech-c: AF312-AP auth: # Filtered mnt-by: MAINT-ID-UPNSBY changed: 20161025 source: APNIC person: Abdullah Fadil address: Jl. Raya Rungkut Madya no 1 address: Gunung Anyar, Surabaya address: Jawa Timur 60294 country: ID phone: +589 e-mail: nic-hdl: AF312-AP mnt-by: MAINT-ID-UPNSBY changed: 20161025 source: APNIC% This query was served by the APNIC Whois Service version 1.69.1-APNICv1r7-SNAPSHOT (WHOIS2). Dear Client, Terlampir beberapa file terkait energi dan batubara: 1. Daftar isi terbaru dari buku “Coal Business in Indonesia, March 2017”. Last update: 12 Maret 2017.
Daftar harga buku-buku terkait energi dan batubara. Saat ini, buku “Coal Business in Indonesia, March 2017. Last update: 12 Maret 2017”, ditawarkan dengan harga US$ 2.000 (dua ribu dollar AS), khusus untuk e-book dengan format pdf, single license. E-book dengan format flash (file.exe) disewakan dengan harga US$ 200 (dua ratus dollar AS) per hari. Dalam prakteknya, e-book flash bisa diakses dalam rentang waktu kurang dari 48 hari. Kelonggaran diberikan karena adanya tenggang waktu (time lapse) antara pembuatan, upload, dan download file e-book flash sampai ke layar monitor pembaca yang membeli.
Tidak ada batasan masa sewa e-book flash. Akan tetapi, e-book flash dibatasi menjadi kadaluwarsa setelah 5 hari. Di hari ke-5, file e-book flash dengan kadaluwarsa tambahan 5 hari berikutnya diharapkan sudah di-upload dengan link baru sudah terkirimkan ke e-mail pembaca yang membeli. Beberapa direktori terkait bisnis batubara sudah tersedia: 1. Direktori usaha tambang dengan status CNC, 2. Direktori perusahaan tambang batubara, 3. Direktori perusahaan tambang batubara dengan status CNC, 4.
Direktori perusahaan eksportir batubara, 5. Direktori perusahaan pengangkut batubara, 6. Direktori usaha batubara, dan lainnya. Setelah analisa dan peng-update-an terakhir ini selesai, buku “Coal Business in Indonesia, April 2017” hanya akan ditawarkan dalam bentuk cetak dan sewa e-book flash.
Tidak ada diskriminasi harga antara pembeli WNI atau WNA. Buku edisi cetak “Coal Business in Indonesia, April 2017” ditawarkan dengan harga US$ 2.500 (dua ribu lima ratus dollar AS). File e-book flash berjudul “Coal Business in Indonesia, April 2017” disewakan dengan harga US$ 250 per hari. Tidak ada batasan masa sewa e-book flash. Akan tetapi, e-book flash dibatasi menjadi kadaluwarsa setelah 5 hari. Di hari ke-5, file e-book flash dengan kadaluwarsa tambahan 5 hari berikutnya diharapkan sudah di-upload dengan link baru sudah terkirimkan ke e-mail pembaca yang membeli. Khusus untuk early bird buyers, saya menawarkan buku “Coal Business in Indonesia, April 2017” dengan harga spesial.
Khusus untuk early bird buyers, bila bapak memerlukan tabel, denah, bagan, grafis, dan gambar dalam buku “Coal Business in Indonesia, April 2017”, saya bisa memberikannya secara gratis dengan beberapa batasan tertentu. Penawaran ini ditutup sampai 31 Maret 2017. Demikian update dan penawaran dari saya. Terima kasih atas perhatian dan kerjasamanya. Salam, Sando Jakarta, 12 Maret 2017 Get the latest announcement of CNC status of mining business in Indonesia and the revoked mining permits ( Daftar CNC ke-23 dan IUP yang Dicabut) in here for free Read the comprehensive report on “ Coal Business in Indonesia” online in Daftar CNC ke-23 & IUP yang dicabut Jakarta, 22 Februari 2017 KEMENTERIAN ENERGI DAN SUMBER DAYA MINERAL REPUBLIK INDONESIA DIREKTORAT JENDERAL MINERAL DAN BATUBARA JALAN PROF. 10 JAKARTA 12870 TELEPON: (021) 8295608 FAKSIMILE: (021) 8297642 E-Mail: KOTAK POS: 4632/KBY Web: PENGUMUMAN NOMOR: 400.Pm/04/DJB/2017 TENTANG PENETAPAN IUP CLEAR AND CLEAN KEDUA PULUH TIGA, DAN DAFTAR IUP YANG DICABUT OLEH PENERBIT IZIN Pada hari ini diumumkan Penetapan IUP Clear and Clean (C&C) ke-duapuluh tiga, pembatalan status C&C, dan daftar IUP yang dicabut oleh penerbit izin sebagaimana terlampir yang telah memenuhi ketentuan sebagaimana yang diatur dalam Peraturan Menteri ESDM Nomor 43 Tahun 2015 (Permen ESDM No.
Peraturan Menteri ESDM Nomor 02 Tahun 2013 sebagai pelaksanaan dari Undang-Undang 4 Tahun 2009, dengan persyaratan IUP yang memenuhi kriteria sebagaimana berikut: 1. Administrasi; 2. Kewilayahan; 3. Teknis dan lingkungan; 4.
Finansial; Penetapan IUP C&C evaluasi daerah diberikan terhadap IUP yang telah dilakukan evaluasi dan mendapatkan rekomendasi dari Gubernur berdasarkan kriteria administrasi dan kewilayahan. Bagi IUP yang telah ditetapkan C&C-nya dan membutuhkan penerbitan sertifikat C&C wajib mendapatkan rekomendasi penerbitan sertifikat dari Gubernur sesuai kriteria yang diatur pada Permen ESDM No.
43/2015, yaitu: 1. Tahap Eksplorasi: Menyampaikan bukti setor iuran tetap sampai dengan tahun terakhir dan rekomendasi hasil evaluasi teknis (Laporan Eksplorasi) dari Pemerintah Provinsi; 2.
Tahapan Operasi Produksi: a. Menyampaikan rekomendasi hasil evaluasi teknis dan lingkungan (Laporan Eksplorasi, Studi Kelayakan, dan Dokumen Lingkungan) dari Pemerintah Provinsi yang dilengkapi dengan:. Scan berwarna / copy cover dokumen AMDAL atau UKL-UPL yang telah disetujui, ditandatangan, dan dilegalisir instansi berwenang;. Copy halaman sub bab batas wilayah studi / sub bab lokasi proyek yang mencakup lokasi proyek, luas wilayah proyek, dan tabel koordinat lokasi. Menyampaikan bukti setor pembayaran iuran tetap dan iuran produksi (royalti) sampai dengan tahun terakhir. Total Rekomendasi C&C dari Provinsi berjumlah 1.352 (seribu tiga ratus lima puluh dua) IUP terdiri dari 1.206 (seribu dua ratus enam) IUP rekomendasi dari Gubernur dan 146 (seratus empat puluh enam) IUP rekomendasi dari Kepala Dinas.
Dari seluruh rekomendasi Gubernur yang memenuhi persyaratan sesuai Permen ESDM No. 43/2015 berjumlah 91 (sembilan puluh satu) IUP, yang belum atau tidak memenuhi persyaratan sesuai Permen ESDM No. 43/2015 berjumlah 661 (enam ratus enam puluh satu) IUP, serta IUP yang telah ditetapkan C&C pada pengumuman-pengumuman C&C sebelumnya berjumlah 454 (empat ratus lima puluh empat) IUP. Rekomendasi Kepala Dinas sejumlah 146 (seratus empat puluh enam) IUP belum dapat dinyatakan C&C karena belum atau tidak memenuhi persyaratan sesuai Permen ESDM No. 43/2015; Penetapan IUP C&C evaluasi pusat diberikan terhadap IUP yang telah dilakukan evaluasi oleh Direktorat Jenderal Mineral dan Batubara berdasarkan kriteria administrasi dan kewilayahan. Bagi IUP yang telah ditetapkan C&C-nya dan membutuhkan penerbitan sertifikat C&C wajib menyampaikan permohonan sesuai kriteria yang diatur pada Permen ESDM No. 43/2015; Pembatalan status C&C sebanyak 38 (tiga puluh delapan) IUP berdasarkan surat usulan pembatalan, SK Pengakhiran dan SK Pencabutan.
Informasi pencabutan/pengakhiran IUP sebanyak 200 (dua ratus) IUP berdasarkan SK Pengakhiran, SK Pencabutan, dan Berita Acara Rekonsiliasi & Sinkronisasi IUP antara Ditjen Minerba, KPK, dan Pemerintah Provinsi; Pengumuman C&C ini berlaku sejak tanggal ditetapkan dan apabila terdapat kekeliruan dalam penentuan C&C ini dan ditemukan fakta baru yang menyatakan bahwa lUP-nya tidak C&C, maka akan dilakukan pembatalan pengumuman sesuai peraturan perundang-undangan yang berlaku. When the goof-old-fashioned Microsoft monetise its Windows Operating Systems by Sando Sasako Jakarta, 19 February 2017 People begin to scramble adopting Linux, in their desperate moves replacing Windows. Eventually, people will stick using Microsoft Windows when the internet still supports them to browse the internet. Otherwise, people will revert back to the goof-old-fashioned Windows XP. At least, that’s what I want to do. My Windows 7 Ultimate (both 32-bit and 64-bit) loves to reset itself, revealing the BSOD messages as the main culprits.
Countless I remain. The most absurd of Windows fatality has been the incapable Microsoft to manage the CLR problem. It means the entire business life of Microsoft’s Windows, that is eversince Windows began to appear as an operating system of a ‘computer’. Windows can never deal with the drivers issues, always stumbles and crashes. Instead to cope with the standard and generic ‘drivers’ that have been pushed by Microsoft to the whole manufacturers worldwide, Windows loves to cease operational and gives it up, waving the white flag right at once, as it senses some drivers issue began to show up a trouble. Windows 10 is ain’t different.
The new Windows 10 changes its colour, its skin mostly, from blue to green. Bien venue the Green Screen of Death. Farewell the Blue Screen of Death. Another desperate move of Microsoft is to monetise its Windows operating systems. Patch Tuesday began to disappear from October 2016 onwards, replaced by a single security-only update through Microsoft Security Bulletins or Microsoft Security Updates.
Quality updates are the terms. Such an oxymoron. As you might have known, every update means cumulating the time bombs for your Windows to k-boom, frying the motherboards, harddrives, graphic cards.
I’m just saying. An update to some Windows fonts can force you to reinstall the whole operating system from the scratch. Those are the botches supplied with and in the past Patch Tuesdays. Microsoft began to insist “No More Pick-and-Choose Patching”. Krebsonsecurity, Microsoft: No More Pick-and-Choose Patching, Oct. 2016, “Windows as a service” means big, painful changes for IT pros By Ed Bott for The Ed Bott Report February 18, 2017 — 16:09 GMT (00:09 GMT+08:00) Everything you know about Windows deployment is undergoing wrenching changes. For IT pros who’ve grown accustomed to “set it and forget it” as a management strategy, three big changes are making life much more challenging.
When Microsoft rolled out the “Windows as a Service” tagline for Windows 10, most of us assumed it was just another marketing ploy. But as we approach Windows 10’s two-year anniversary, it’s becoming apparent that there’s some substance behind the label.
And for Windows power users and IT pros, the ramifications are just beginning to become apparent. Microsoft has published a handful of low-key technical articles covering the new rules, but some of those details have shifted over time. The maximum interval for deferring feature updates, for example, was eight months when the feature debuted in November 2015, but shrank to 180 days in the July 2016 Anniversary Update. Even for those of us who regularly attend IT-focused conferences and keep up with deployment news, managing a Windows-based organization in this new era can be confusing. For those who are simply using Windows for day-to-day-business, the changes can appear unexpectedly.
And the realization that tried-and-true workflows no longer apply isn’t sitting well with some IT pros. For the past year, I’ve been hearing a steady stream of complaints from longtime Windows admins and users. Consistently, those grumbles all boil down to a single objection: Because of “Windows as a service,” we’re losing control of our desktop PCs. They have a point. For the past quarter-century, businesses running Windows have been able to count on a few constants, all of which are now changing.
Consider these three major shifts: Overly aggressive upgrade cycles It used to be that you could install your preferred version of Windows and stick with it for nearly a decade. If you deployed Windows 7 Service Pack 1 when it was released in February 2011, for example, its feature set has been constant for the past six years and will remain unchanged for the remaining three years of its supported life. In the new world, that upgrade cycle has shrunk to roughly 18 months, thanks to feature updates (the new term for upgrades) that can be deferred but not refused.
This slide from a Microsoft presentation shows the support lifecycle for a Windows 10 feature update: Image credit: Microsoft Here’s how it works in practice: If you upgraded to Windows 10 Pro one year ago, in February 2016, you got the latest release, version 1511. Six months later, Microsoft released the Anniversary Update, version 1607, to the Current Branch (CB). That version was released to the Current Branch for Business (CBB) on November 29, 2016. An option available only in business versions (Pro/Enterprise/Education) allows you to defer feature updates until they’re released to the Current Branch for Business.
Using Group Policy, you can defer those updates by an additional eight months in version 1511. That means you’ll be forced to upgrade to version 1607 or later in July 2017, less than a year and a half after your initial deployment. And that upgrade cycle is going to get tighter. In version 1607, the Group Policy to defer updates shrinks from eight months to 180 days, with a 60-day grace period at the end. In addition, Microsoft has hinted that it plans to ship two feature updates per year starting in 2017. The upshot is that you should expect to upgrade every PC in your organization roughly once a year.
That’s a big change. For small businesses that don’t have the time or technical expertise to test each new feature update in advance, it can result in major disruptions if an update breaks compatibility with a business-critical third-party app. All-or-nothing updates In the good old days, each month’s Patch Tuesday collection consisted of an assortment of individual updates from which you could pick and choose.
The new Windows Update model packages all those security and reliability fixes into cumulative updates that can’t be unbundled. Here, too, you can only postpone installation for a few weeks. “No, thanks” is not an option for an individual update. That design has been part of Windows 10 from the start, and in recent months it’s shifted to Windows 7 and Windows 8.1 as well. As a result, checking Windows Update on a Windows 7 PC today no longer returns a lengthy list of individual updates; instead, you get a single rollup like the one shown here. Cumulative updates are the new standard in all supported Windows versions.
Microsoft’s justification for this new approach makes sense, at least in theory. When Windows engineers test a new update, they use a fully patched system as the baseline. There’s no way to confirm that an update will work on a PC where you’ve been selectively applying updates. So the new model is designed to drag the entire installed base of Windows PCs, kicking and screaming if necessary, to the same baseline configuration. This new model will take some careful attention from IT pros, who will no longer have the option to solve a compatibility problem by uninstalling a problematic update. Using Group Policy, you can defer updates for up to 30 days as you test, but if you find a problem the only option is to delay the update for a few weeks, which means you’re also skipping potentially critical security fixes.
The cumulative update model is also causing some teething pains in Redmond, where an undisclosed problem in February 2017 forced Microsoft to skip an entire Patch Tuesday cycle for the first time in history. The death of the service pack Windows 7 still has nearly three years left in its support lifecycle, but the one and only service pack was released more than six years ago. If you don’t know the secret recipe of updates to install, a fresh installation of Windows 7 can take several days to be fully updated. With Windows 10, Microsoft regularly releases new installation media (in ISO format) reflecting the latest feature update. But OEM recovery partitions aren’t automatically updated, which means if you roll back an OEM device to its original factory configuration you have to download several gigabytes for the latest feature update and then another very large cumulative update to bring it current. The bottom line with all these changes is that IT pros who’ve been used to running Windows in set-it-and-forget-it mode are going to have to begin paying closer attention, not just to what’s in this month’s updates but what’s in the pipeline for the next year.
And don’t expect Microsoft to back down on any of these decisions. There are minor changes in the pipeline to make it easier to schedule updates, but the underlying servicing and deployment models aren’t likely to change. If you’re not paying attention, be prepared for some surprises. On November 29, 2016. Secret recipe of updates to install Overview of Windows as a service Dani Halfin, Last Updated: 2/9/2017 Applies to Windows 10 Windows 10 Mobile Windows 10 IoT Mobile The Windows 10 operating system introduces a new way to build, deploy, and service Windows: Windows as a service.
Microsoft has reimagined each part of the process, to simplify the lives of IT pros and maintain a consistent Windows 10 experience for its customers. These improvements focus on maximizing customer involvement in Windows development, simplifying the deployment and servicing of Windows client computers, and leveling out the resources needed to deploy and maintain Windows over time. Building Prior to Windows 10, Microsoft released new versions of Windows every few years. This traditional deployment schedule imposed a training burden on users because the feature revisions were often significant. That schedule also meant waiting long periods without new features – a scenario that doesn’t work in today’s rapidly changing world, a world in which new security, management, and deployment capabilities are necessary to address challenges. Windows as a service will deliver smaller feature updates two to three times per year to help address these issues.
In the past, when Microsoft developed new versions of Windows, it typically released technical previews near the end of the process, when Windows was nearly ready to ship. With Windows 10, new features will be delivered to the Windows Insider community as soon as possible – during the development cycle, through a process called flighting – so that organizations can see exactly what Microsoft is developing and start their testing as soon as possible. Microsoft also depends on receiving feedback from organizations throughout the development process so that it can make adjustments as quickly as possible rather than waiting until after release.
For more information about the Windows Insider Program and how to sign up, see the section Windows Insider. Of course Microsoft also performs extensive internal testing, with engineering teams installing new builds daily, and larger groups of employees installing builds frequently, all before those builds are ever released to the Windows Insider Program.
Deploying Deploying Windows 10 is simpler than with previous versions of Windows. When migrating from earlier versions of Windows, an easy in-place upgrade process can be used to automatically preserve all apps, settings, and data. And once running Windows 10, deployment of Windows 10 feature updates will be equally simple.
One of the biggest challenges for organizations when it comes to deploying a new version of Windows is compatibility testing. Whereas compatibility was previously a concern for organizations upgrading to a new version of Windows, Windows 10 is compatible with most hardware and software capable of running on Windows 7 or later. Because of this high level of compatibility, the app compatibility testing process can be greatly simplified. Application compatibility Application compatibility testing has historically been a burden when approaching a Windows deployment or upgrade.
With Windows 10, application compatibility from the perspective of desktop applications, websites, and apps built on the Universal Windows Platform (UWP) has improved tremendously. Microsoft understands the challenges organizations experienced when they migrated from the Windows XP operating system to Windows 7 and has been working to make Windows 10 upgrades a much better experience.
Most Windows 7-compatible desktop applications will be compatible with Windows 10 straight out of the box. Windows 10 achieved such high compatibility because the changes in the existing Win32 application programming interfaces were minimal. Combined with valuable feedback via the Windows Insider Program and telemetry data, this level of compatibility can be maintained through each feature update. As for websites, Windows 10 includes Internet Explorer 11 and its backward-compatibility modes for legacy websites. Finally, UWP apps follow a compatibility story similar to desktop applications, so most of them will be compatible with Windows 10. For the most important business-critical applications, organizations should still perform testing on a regular basis to validate compatibility with new builds. For remaining applications, consider validating them as part of a pilot deployment process to reduce the time spent on compatibility testing.
If it’s unclear whether an application is compatible with Windows 10, IT pros can either consult with the ISV or check the supported software directory at. Device compatibility Device compatibility in Windows 10 is also very strong; new hardware is not needed for Windows 10 as any device capable of running Windows 7 or later can run Windows 10. In fact, the minimum hardware requirements to run Windows 10 are the same as those required for Windows 7. Most hardware drivers that functioned in Windows 8.1, Windows 8, or Windows 7 will continue to function in Windows 10. Servicing Traditional Windows servicing has included several release types: major revisions (e.g., the Windows 8.1, Windows 8, and Windows 7 operating systems), service packs, and monthly updates.
With Windows 10, there are two release types: feature updates that add new functionality two to three times per year, and quality updates that provide security and reliability fixes at least once a month. With Windows 10, organizations will need to change the way they approach deploying updates. Servicing branches are the first way to separate users into deployment groups for feature and quality updates. With the introduction of servicing branches comes the concept of a deployment ring, which is simply a way to categorize the combination of a deployment group and a servicing branch to group devices for successive waves of deployment. For more information about developing a deployment strategy that leverages servicing branches and deployment rings, see Plan servicing strategy for Windows 10 updates. For information about each servicing tool available for Windows 10, see Servicing tools.
To align with this new update delivery model, Windows 10 has three servicing branches, each of which provides different levels of flexibility over when these updates are delivered to client computers. For information about the servicing branches available in Windows 10, see Servicing branches. Feature updates With Windows 10, Microsoft will package new features into feature updates that can be deployed using existing management tools. Because feature updates are delivered more frequently than with previous Windows releases – two to three times per year rather than every 3-5 years – changes will be in bite-sized chunks rather than all at once and end user readiness time much shorter. Quality updates Monthly updates in previous Windows versions were often overwhelming because of the sheer number of updates available each month. Many organizations selectively chose which updates they wanted to install and which they didn’t, and this created countless scenarios in which organizations deployed essential security updates but picked only a subset of nonsecurity fixes.
In Windows 10, rather than receiving several updates each month and trying to figure out which the organization needs, which ultimately causes platform fragmentation, administrators will see one cumulative monthly update that supersedes the previous month’s update, containing both security and nonsecurity fixes. This approach makes patching simpler and ensures that customers’ devices are more closely aligned with the testing done at Microsoft, reducing unexpected issues resulting from patching. The left side of Figure 1 provides an example of Windows 7 devices in an enterprise and what their current patch level might look like. On the right is what Microsoft’s test environment PCs contain. This drastic difference is the basis for many compatibility issues and system anomalies related to Windows updates. Figure 1 – Comparison of patch environment in enterprise compared to test Servicing branches To align with the new method of delivering feature updates and quality updates in Windows 10, Microsoft introduced the concept of servicing branches to allow customers to designate how aggressively their individual devices are updated.
For example, an organization may have test devices that the IT department can update with new features as soon as possible, and then specialized devices that require a longer feature update cycle to ensure continuity. With that in mind, Microsoft offers three servicing branches for Windows 10: Current Branch (CB), Current Branch for Business (CBB), and Long-Term Servicing Branch (LTSB). In addition, the Windows Insider Program provides IT pros and other interested parties with prerelease Windows builds that they can test and ultimately provide feedback on to Microsoft. For details about the versions in each servicing branch, see Windows 10 release information. The concept of servicing branches is new, but organizations can use the same management tools they used to manage updates and upgrades in previous versions of Windows.
For more information about the servicing tool options for Windows 10 and their capabilities, see Servicing tools. Note Servicing branches are not the only way to separate groups of devices when consuming updates. Each branch can contain subsets of devices, which staggers servicing even further. For information about the servicing strategy and ongoing deployment process for Windows 10, including the role of servicing branches, see Plan servicing strategy for Windows 10 updates.
Current Branch In the CB servicing model, feature updates are available as soon as Microsoft releases them. Windows 10 version 1511 had few servicing tool options to delay CB feature updates, limiting the use of the CB servicing branch.
Windows 10 version 1607, however, includes more servicing tools that can delay CB feature updates for up to 180 days. The CB servicing model is ideal for pilot deployments and testing of Windows 10 feature updates and for users such as developers who need to work with the latest features immediately. When Microsoft officially releases a feature update for Windows 10, that update is marked for CB, making it available to any PC not configured to defer feature updates so that those devices can immediately install it. Organizations that use Windows Server Update Services (WSUS), Microsoft System Center Configuration Manager, or Windows Update for Business, however, can defer CB feature updates to selective devices by withholding their approval and deployment. In this scenario, the content available for CB will be available but not necessarily immediately mandatory, depending on the policy of the management system.
Only one CB build of Windows is supported at a time, so those clients not on the most current build will not receive quality updates (after a 60 day grace period) until the most current feature update has been installed. For more details about Windows 10 servicing tools, see Servicing tools.
Current Branch for Business Organizations typically prefer to have a testing cycle before broadly deploying new features to business users. For Windows 10, most pilot testing will be done using the CB servicing branch.
In contrast, the CBB servicing branch is typically used for broad deployment. Windows 10 clients in the CBB servicing branch receive the same build of Windows 10 as those in the CB servicing branch, just at a later time. CB releases are transitioned to CBB after about 4 months, indicating that Microsoft, independent software vendors (ISVs), partners, and customers believe that the release is ready for broad deployment. Therefore, CB and CBB have an inherent “staging” effect. Both of these branches have a purpose in the overall deployment process for an enterprise, providing another layer of testing capabilities in addition to the traditional phased deployment methods to specific groups of machines.
Microsoft will support two CBB builds at a time, plus a 60 day grace period. Each feature update release will be supported and updated for a minimum of 18 months. Note Organizations can electively delay CB and CBB updates into as many phases as they wish by using one of the servicing tools mentioned in the section Servicing tools. Basically, CBB is a configuration state, meaning that if a computer has the Defer Updates and Upgrades flag enabled-either through Group Policy, a mobile device management product like Microsoft Intune, or manually on the client-it’s considered to be in the CBB servicing branch. The benefit of tying this servicing model and CB to a configuration state rather than a SKU is that they are easily interchangeable. If an organization accidentally selects CBB on a machine that doesn’t need delayed updates, it’s simple to change it back.
Long-term Servicing Branch Specialized systems-such as PCs that control medical equipment, point-of-sale systems, and ATMs-often require a longer servicing option because of their purpose. These devices typically perform a single important task and don’t need feature updates as frequently as other devices in the organization. It’s more important that these devices be kept as stable and secure as possible than up to date with user interface changes. The LTSB servicing model prevents Windows 10 Enterprise LTSB devices from receiving the usual feature updates and provides only quality updates to ensure that device security stays up to date. With this in mind, quality updates are still immediately available to Windows 10 Enterprise LTSB clients, but customers can choose to defer them by using one of the servicing tools mentioned in the section Servicing tools.
Note LTSB is not intended for deployment on most or all the PCs in an organization; it should be used only for special-purpose devices. As a general guideline, a PC with Microsoft Office installed is a general-purpose device, typically used by an information worker, and therefore it is better suited for the CB or CBB servicing branch.
Microsoft never publishes feature updates through Windows Update on devices that run Windows 10 Enterprise LTSB. Instead, it typically offers new LTSB releases every 2-3 years, and organizations can choose to install them as in-place upgrades or even skip releases over a 10-year life cycle. Note Windows 10 LTSB will support the currently released silicon at the time of release of the LTSB. As future silicon generations are released, support will be created through future Windows 10 LTSB releases that customers can deploy for those systems. For more information, see Supporting the latest processor and chipsets on Windows in Lifecycle support policy FAQ – Windows Products.
LTSB is available only in the Windows 10 Enterprise LTSB edition. This build of Windows doesn’t contain many in-box applications, such as Microsoft Edge, Windows Store client, Cortana (limited search capabilities remain available), Microsoft Mail, Calendar, OneNote, Weather, News, Sports, Money, Photos, Camera, Music, and Clock. Therefore, it’s important to remember that Microsoft has positioned the LTSB model primarily for specialized devices. Note If an organization has devices currently running Windows 10 Enterprise LTSB that it would like to change to the CB or CBB servicing branch, it can make the change without losing user data. Because LTSB is its own SKU, however, an upgrade is required from Windows 10 Enterprise LTSB to Windows 10 Enterprise, which supports CB and CBB.
Windows Insider For many IT pros, gaining visibility into feature updates early-before they’re available to the CB servicing branch-can be both intriguing and valuable for future end user communications as well as provide additional prestaging for CB machines. With Windows 10, feature flighting enables Windows Insiders to consume and deploy preproduction code to their test machines, gaining early visibility into the next build.
Testing the early builds of Windows 10 helps both Microsoft and its customers because they have the opportunity to discover possible issues before the update is ever publicly available and can report it to Microsoft. Also, as flighted builds get closer to their release to CB, organizations can test their deployment on test devices for compatibility validation. Microsoft recommends that all organizations have at least a few PCs enrolled in the Windows Insider Program and provide feedback on any issues they encounter. For information about how to sign up for the Windows Insider Program and enroll test devices, go to. Note Microsoft recommends that all organizations have at least a few PCs enrolled in the Windows Insider Program, to include the Windows Insider Program in their deployment plans and to provide feedback on any issues they encounter to Microsoft via our Feedback Hub app. The Windows Insider Program isn’t intended to replace CB deployments in an organization.
Rather, it provides IT pros and other interested parties with pre-release Windows builds that they can test and ultimately provide feedback on to Microsoft. Servicing tools There are many tools with which IT pros can service Windows as a service.
Each option has its pros and cons, ranging from capabilities and control to simplicity and low administrative requirements. The following are examples of the servicing tools available to manage Windows as a service updates: Windows Update (stand-alone) provides limited control over feature updates, with IT pros manually configuring the device to be in the CBB servicing branch. Organizations can control which devices defer updates and stay in the CBB servicing branch or remain in CB by selecting the Defer upgrades check box in Start Settings Update & Security Advanced Options on a Windows 10 client.
Windows Update for Business is the second option for servicing Windows as a service. This servicing tool includes a little more control over update deferment and provides centralized management using Group Policy.
In Windows 10 version 1511, Windows Update for Business can be used to defer feature updates for up to 8 months and quality updates for up to 4 weeks. Also, these deferment options were available only to clients in the CBB servicing branch. In Windows 10 version 1607 and later, Windows Update for Business can be used to defer feature updates for up to 180 days and quality updates for up to 30 days. These deployment options are available to clients in either the CB or CBB servicing branch. In addition to being able to use Group Policy to manage Windows Update for Business, either option can be configured without requiring any on-premises infrastructure by using Intune. Windows Server Update Services (WSUS) provides extensive control over Windows 10 updates and is natively available in the Windows Server operating system. In addition to the ability to defer updates, organizations can add an approval layer for updates and choose to deploy them to specific computers or groups of computers whenever ready.
System Center Configuration Manager provides the greatest control over servicing Windows as a service. IT pros can defer updates, approve them, and have multiple options for targeting deployments and managing bandwidth usage and deployment times. With all these options, which an organization chooses depends on the resources, staff, and expertise its IT organization already has. For example, if IT already uses System Center Configuration Manager to manage Windows updates, it can continue to use it.
Similarly, if IT is using WSUS, it can continue to use that. For a consolidated look at the benefits of each tool, see Table 1. Table 1 Servicing tool Can updates be deferred?