In Microsoft Intune, “Retire,” “Wipe,” and “Delete” are actions you can take when managing mobile devices and sometimes computers. These actions are used to control and secure the data and settings on the devices.
1- Retire:
Purpose: Retiring a device means marking it as no longer needed or in use. It’s a way to indicate that the device is no longer managed by the organization.
Effects: When you retire a device, it typically removes company data and settings associated with that device, but it doesn’t wipe the entire device or delete personal data.
Use Case: You would use the retirement option when an employee leaves the company, and you want to remove their access to company resources without wiping their personal data.
2- Wipe:
Purpose: Wiping a device means removing all data and settings on the device, returning it to its factory state. It’s a more drastic action than retiring and is typically used in cases where the device is lost, stolen, or when more thorough data removal is necessary.
Effects: Wiping a device will erase all data on the device, including both company and personal data. It resets the device to its original configuration.
Use Case: You would use the wipe option when a device is lost or stolen, or when you need to decommission a device and ensure no company data remains on it.
3- Delete:
Purpose: Deleting a device removes it from the Intune console and revokes its management capabilities. It’s a way to permanently remove a device from the organization’s Intune account.
Effects: Deleting a device removes it from management but does not wipe the device or affect the data on it.
Use Case: You would use the delete option when you no longer need to manage a device with Intune, such as when a device is no longer in use or is being replaced.
The difference between ‘Retire’, ‘Wipe’, and ‘Delete’ in Intune device management is as follows:
Retire:
removes app data, settings, and Intune managed email profiles from the device. The device will still show up in Intune until the device checks in. Retirement leaves users’ personal data on the device. Retire also removes the Azure AD record of the device, unless the device has an Autopilot hash assigned³.
Wipe :
restores a device to its factory default settings. All data, apps, and settings are removed. Wipe also removes the device from Intune management and Azure AD, unless the device has an Autopilot hash assigned³. Wipe is useful for resetting a device before giving it to a new user, or when the device has been lost or stolen.
Delete:
removes the device from the All-devices list in Intune immediately. Delete also issues the retire command to the device, which removes app data, settings, and Intune managed email profiles from the device. Delete also removes the Azure AD record of the device, unless the device has an Autopilot hash assigned³.
It’s important to understand the differences between these actions and use them appropriately based on your organization’s policies and the specific circumstances for each device. Always exercise caution when performing actions like wiping or deleting, as they can result in data loss on the device. It’s also good practice to communicate with the device owner or user before taking such actions, especially when dealing with personal devices.
Installing Active Directory on a Windows Server involves several steps. Active Directory is a directory service provided by Microsoft for Windows network environments. It allows you to manage users, computers, and other network resources in a centralized and secure manner. Here’s a step-by-step guide on how to install Active Directory on a Windows Server:
Note: You’ll need to have a Windows Server operating system installed on your server before you can install Active Directory. Additionally, make sure your server has a static IP address and DNS settings configured correctly.
Open Server Manager:
Log in to your Windows Server, and the first step is to open the Server Manager. You can usually find it on the taskbar or in the Start menu.
Add Roles and Features:
In Server Manager, click on “Manage” in the top-right corner and select “Add Roles and Features.”
Click “Next” on the “Before you begin” page.
Installation Type:
Choose “Role-based or feature-based installation” and click “Next.”
Destination Server:
Select the server where you want to install Active Directory and click “Next.”
Server Roles:
Scroll down and find “Active Directory Domain Services.” Check the box next to it.
A dialog box will pop up asking you to add features that are required for Active Directory Domain Services. Click “Add Features.”
Click “Next.”
Add Features (Optional):
If prompted to add any required features, simply click “Next.”
Active Directory Domain Services:
Read the information provided about Active Directory Domain Services and click “Next.”
Confirm Installation Selections:
Review your selections. If everything looks correct, click “Install.”
Installation Progress:
The installation process will begin. It may take a few minutes.
Installation Results:
After the installation is complete, you should see a “Installation succeeded” message. Click “Promote this server to a domain controller.”
Deployment Configuration:
In the “Deployment Configuration” section, select “Add a new forest” if you are creating a new Active Directory Forest. If you are adding this server to an existing forest, select the appropriate option.
Enter a root domain name for your Active Directory Forest (e.g., mydomain.local). Choose a name that is unique to your network.
Set a Directory Services Restore Mode (DSRM) password. This is a critical password used for recovery purposes.
Click “Next.”
Domain Controller Options :
Choose the appropriate options for your environment, such as DNS and Global Catalog. The default options are usually suitable for most scenarios.
If your server is the first domain controller in your environment, it will automatically become the DNS server.
Click “Next.”
Additional Options:
Configure any additional options as needed for your environment. These options include the paths for the Active Directory database, log files, and system volume (SYSVOL).
Review the summary of your selections and click “Next.”
Review Options and Prerequisites:
The system will perform a prerequisite check. Ensure there are no errors or warnings and click “Install” to proceed.
Active Directory Installation:
The installation process will begin, and your server will be configured as a domain controller.
Completion:
Once the installation is complete, your server will restart.
After the server restarts, Active Directory will be installed and ready for use. You can then start managing users, groups, and other directory objects through Active Directory Users and Computers, which can be found in the Administrative Tools or accessed through Server Manager.
To add a new user in Azure Active Directory (Azure AD), you typically have a few different methods to choose from, depending on your needs and preferences. Here’s a common method using the Azure portal:
Sign in, to Azure Portal:
Sign in, to your Azure portal using your admin account
Access Azure Active Directory :
Click on “Azure Active Directory” in the left-hand menu. If you can’t find it, you can also use the search bar to locate it quickly.
Add a New User:
There are a few ways to add a new user, but the most common one is to go to “Users” under “Manage.” Click on the “+ New user” button. With two ways we can create user:
Create user
Invite user
User Details:
You’ll be prompted to enter the user’s details. These typically include:
Username: The user’s username, which is used for signing in.
Name: Full name of the user.
Profile: You can set the user’s job title, department, and more.
User type: Depending on your subscription, you can choose between “Member,” “Guest,” or “External.”
Authentication and Role Assignment:
You’ll set the user’s role and authentication method. Here, you can choose roles like “User” or “Global Administrator.” You’ll also set their password and authentication method, whether it’s a temporary password or you let them create their own.
Directory Role:
Depending on your needs, you might want to assign the user to directory roles, like “User administrator” or “Application administrator.”
Groups:
You can also add the user to Azure AD security groups if needed.
Review and Create:
Review the user’s details and settings. Make sure everything is correct.
Create:
Once you’re satisfied, click “Create” to add the user to Azure AD.
The user should now be added to Azure AD. They will receive an email (if you provided their email address) to set up their account or change their temporary password.
Please note that the specific steps and options may vary depending on the version of Azure and your subscription level. Always ensure that you have the necessary permissions and follow best practices for user management and security in your organization.
It also known as additive manufacturing, has a rich history that dates back several decades. Here’s a brief overview of the key milestones in the history of 3D printing, along with some images to illustrate its evolution:
Charles W. Hull
1960s
Invention of Stereolithography (SLA):
The concept of this printers began with the invention of stereolithography by Charles W. Hull in 1983. He later co-founded 3D Systems, a pioneering 3D printing company.
1980s
Fused Deposition Modeling (FDM) Patented:
Scott Crump patented Fused Deposition Modeling in the late 1980s, which laid the foundation for the development of desktop printers.
Scott Crump
1990s
3D Printing Industry Emerges:
During the 1990s, several 3D printer technologies and companies emerged, including selective laser sintering (SLS) and the formation of Stratasys.
2000s
Rise of Desktop Printers :
The 2000s saw the development of more accessible desktop printers, making the technology available to a wider audience.
2010s
Expanding Applications:
3D printing began to revolutionize various industries, including aerospace, healthcare, and automotive. Customized prosthetics, dental implants, and aerospace components were being printed.
2020s
Advancements Continue:
The 2020s have witnessed ongoing advancements in printers’ materials, speed, and precision, expanding its applications even further.
Future
Printing in Space and More:
The future of these printers holds promises for applications in space exploration, construction, and personalized medicine.
These images and milestones provide a glimpse into the history and evolution of its technology. It has come a long way since its inception and continues to shape industries and innovation across the globe.
In this tutorial we want to learn how we can add Application in Intune (for windows)? To add an app in Microsoft Intune, you can follow these general steps:
Sign into the Microsoft Endpoint Manager admin center (https://endpoint.microsoft.com) using your administrator account.
Navigate to “Apps” from the left-hand menu.
Click on “Add” to start the process of adding a new app.
Select the app type you want to add. Intune supports several types of apps, including “Managed Google Play app,” “iOS/iPadOS app,” “Android app,” “Windows app (Win32),” “Windows app (store),” and more. Choose the appropriate app type based on your requirements.
Configure the app settings based on the selected app type. The settings may vary depending on the platform and app type. Fill in the required information such as app name, description, publisher, version, installation requirements, etc. Some app types may require additional configuration, such as app package upload or linking to the app store.
Specify the deployment settings, including the targeted user or device groups, installation or assignment options, and any additional settings specific to the app type. These settings determine how the app will be deployed to the managed devices.
Review the settings and make any necessary adjustments.
Click on “Add” or “Save” to add the app to Intune.
Once the app is added, it will be available for deployment to the targeted devices or users based on the settings you configured. Users will then be able to install or access the app through the Intune Company Portal or the managed app store on their devices.
Please note that the specific steps and options may vary slightly depending on the version of Microsoft Intune and the app type you are adding.
