Mapping linux drive to windows 8.1 PC


 Share

Recommended Posts

Draconian Guppy

Warning, extreme linux noob here

NP.. SAMBA shares are awesome ;) sudo apt-get install samba :p

 

I am in the early process of converting my Win ServR2 box over for Sickbeard.. 

 

 

Use the Samba GUI, and you'll see how easy it is.

 

 

You ever used network shares in Windows (e.g. "\\MyPC\shared videos")? Samba is the Linux port of that, and the two are mostly compatible. I think in Ubuntu, Samba is integrated into Nautilus. You can just right click -> properties on a folder and share it.

 

EDIT: https://www.liberiangeek.net/2011/11/a-quick-way-to-share-folders-in-ubuntu-11-10-oneiric-ocelot/. This is for Oneiric, but presumably it still applies in Trusty.

 

 

You don't have to manually install it like that. Just use your distro's package manager. Either 'sudo apt-get install samba', 'yaourt -S samba', or something similar. If you're adverse to the cli, most distros come with a GUI that does the equivalent.

 

 

So fed up with windows drivers (ati) I decided to give ubuntu 14.04 a go. So I created all the necessary partitions (and managed to keep my existing ntfs info! ) that process was pretty straight forward booting from USB. I use this PC mostly as an internal fileserver over lan.

 

 

I tried right clicking creating a new share, tried via terminal, tried editing the conf. I got 3 different results, none accessible, see below:

 

YWd54Kt.jpg

 

 

 

Here's my smb.conf, which I basically did not modify, just to add another folder at the end.

 

 

 

 
#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which 
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic 
# errors. 
 
#======================= Global Settings =======================
 
[global]
 
## Browsing/Identification ###
 
# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = WORKGROUP
 
# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)
 
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
#   wins support = no
 
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;   wins server = w.x.y.z
 
# This will prevent nmbd to search for NetBIOS names through DNS.
   dns proxy = no
 
#### Networking ####
 
# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;   interfaces = 127.0.0.0/8 eth0
 
# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;   bind interfaces only = yes
 
 
 
#### Debugging/Accounting ####
 
# This tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/log.%m
 
# Cap the size of the individual log files (in KiB).
   max log size = 1000
 
# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
#   syslog only = no
 
# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
   syslog = 0
 
# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d
 
 
####### Authentication #######
 
# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller". 
#
# Most people will want "standalone sever" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
   server role = standalone server
 
# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.  
   passdb backend = tdbsam
 
   obey pam restrictions = yes
 
# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
   unix password sync = yes
 
# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
 
# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
   pam password change = yes
 
# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
   map to guest = bad user
 
########## Domains ###########
 
#
# The following settings only takes effect if 'server role = primary
# classic domain controller', 'server role = backup domain controller'
# or 'domain logons' is set 
#
 
# It specifies the location of the user's
# profile directory from the client point of view) The following
# required a [profiles] share to be setup on the samba server (see
# below)
;   logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
#   logon path = \\%N\%U\profile
 
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;   logon drive = H:
#   logon home = \\%N\%U
 
# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;   logon script = logon.cmd
 
# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u
 
# This allows machine accounts to be created on the domain controller via the 
# SAMR RPC pipe.  
# The following assumes a "machines" group exists on the system
; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u
 
# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.  
; add group script = /usr/sbin/addgroup --force-badname %g
 
############ Misc ############
 
# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
;   include = /home/samba/etc/smb.conf.%m
 
# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
;   idmap uid = 10000-20000
;   idmap gid = 10000-20000
;   template shell = /bin/bash
 
# Setup usershare options to enable non-root users to share folders
# with the net usershare command.
 
# Maximum number of usershare. 0 (default) means that usershare is disabled.
;   usershare max shares = 100
 
# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
   usershare allow guests = yes
 
#======================= Share Definitions =======================
 
# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[homes]
;   comment = Home Directories
;   browseable = no
 
# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
;   read only = yes
 
# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
;   create mask = 0700
 
# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
;   directory mask = 0700
 
# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# Un-comment the following parameter to make sure that only "username"
# can connect to \\server\username
# This might need tweaking when using external authentication schemes
;   valid users = %S
 
# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
;   comment = Network Logon Service
;   path = /home/samba/netlogon
;   guest ok = yes
;   read only = yes
 
# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no
;   create mask = 0600
;   directory mask = 0700
 
[printers]
   comment = All Printers
   browseable = no
   path = /var/spool/samba
   printable = yes
   guest ok = no
   read only = yes
   create mask = 0700
 
# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin
 
[Guppy]
path = /home/guppy/Desktop/guppy
available = yes
valid users = guppy
read only = no
browsable = yes
public = yes
writable = yes
 

 

Link to post
Share on other sites

Haggis

I have a guide i use in the house, i will find it when i get in and pop it to you

  • Like 1
Link to post
Share on other sites

Haggis

here is mine if it helps

#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which 
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic 
# errors. 
# A well-established practice is to name the original file
# "smb.conf.master" and create the "real" config file with
# testparm -s smb.conf.master >smb.conf
# This minimizes the size of the really used smb.conf file
# which, according to the Samba Team, impacts performance
# However, use this with caution if your smb.conf file contains nested
# "include" statements. See Debian bug #483187 for a case
# where using a master file is not a good idea.
#

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = MSHOME

# server string is the equivalent of the NT Description field
   server string = %h server

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
#   wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;   wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.
   dns proxy = no

# What naming service and in what order should we use to resolve host names
# to IP addresses
;   name resolve order = lmhosts host wins bcast

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;   interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;   bind interfaces only = yes



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
   max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
#   syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
   syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
#   security = user

# You may wish to use password encryption.  See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
   encrypt passwords = true

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.  
   passdb backend = tdbsam

   obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
   unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
   pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
   map to guest = bad user

########## Domains ###########

# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
;   domain logons = yes
#
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
;   logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
#   logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;   logon drive = H:
#   logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;   logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the 
# SAMR RPC pipe.  
# The following assumes a "machines" group exists on the system
; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.  
; add group script = /usr/sbin/addgroup --force-badname %g

########## Printing ##########

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
#   load printers = yes

# lpr(ng) printing. You may wish to override the location of the
# printcap file
;   printing = bsd
;   printcap name = /etc/printcap

# CUPS printing.  See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
;   printing = cups
;   printcap name = cups

############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
;   include = /home/samba/etc/smb.conf.%m

# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
#         SO_RCVBUF=8192 SO_SNDBUF=8192
#   socket options = TCP_NODELAY

# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
;   message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &

# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
#   domain master = auto

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
;   idmap uid = 10000-20000
;   idmap gid = 10000-20000
;   template shell = /bin/bash

# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
;   winbind enum groups = yes
;   winbind enum users = yes

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
;   usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
   usershare allow guests = yes

#======================= Share Definitions =======================

[homes]
   comment = Home Directories
   browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
   read only = no

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
   create mask = 0775

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
   directory mask = 0775

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# The following parameter makes sure that only "username" can connect
# to \\server\username
# This might need tweaking when using external authentication schemes
   valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
;   comment = Network Logon Service
;   path = /home/samba/netlogon
;   guest ok = yes
;   read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no
;   create mask = 0600
;   directory mask = 0700

[printers]
   comment = All Printers
   browseable = no
   path = /var/spool/samba
   printable = yes
   guest ok = no
   read only = yes
   create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin

# A sample share for sharing your CD-ROM with others.
;[cdrom]
;   comment = Samba server's CD-ROM
;   read only = yes
;   locking = no
;   path = /cdrom
;   guest ok = yes

[TV-Shows]
   comment = Some useful files
   read only = no
   locking = no
   path = /home/tv-shows
   guest ok = no

[Movies]
   comment = Some useful files
   read only = no
   locking = no
   path = /home/media
   guest ok = no
# The next two parameters show how to auto-mount a CD-ROM when the
#	cdrom share is accesed. For this to work /etc/fstab must contain
#	an entry like this:
#
#       /dev/scd0   /cdrom  iso9660 defaults,noauto,ro,user   0 0
#
# The CD-ROM gets unmounted automatically after the connection to the
#
# If you don't want to use auto-mounting/unmounting make sure the CD
#	is mounted on /cdrom
#
;   preexec = /bin/mount /cdrom
;   postexec = /bin/umount /cdrom

  • Like 1
Link to post
Share on other sites

Draconian Guppy

thanks, Ill check as soon as  I get home.

Link to post
Share on other sites

Draconian Guppy

fixed using this:

 

If you?re unable to access the shares, go back to your Ubuntu machine and run the commands below:

sudo smbpasswd -a USERNAME

quick_share_oneiric_6_thumb.png

Replace USERNAME with your account name.

 

Now try again to access the shares from your Windows machine

 

To find your computer name in Ubuntu run the command below:

hostname

 

Enjoy!

 

 

Can't add tech points to myself eh?

Link to post
Share on other sites

Draconian Guppy

Cool thanks! 

  • Like 1
Link to post
Share on other sites

This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By News Staff
      Get this free Linux Cheat Sheet Bundle
      by Steven Parker

      Claim your complimentary free cheat sheet, before the offer expires.



      A free collection of downloadable cheat sheets to help you get the most from Linux.

      Linux is a free and open source operating system. It's been around since 1991, but it continues to be an important alternative choice away from Windows and Mac.



      We've put together this collection of cheat sheets that you can download and print off to keep by your side. They'll help you navigate the operating system and its programs effectively and get the most out of them.

      This bundle contains:

      Chrome OS shortcuts Linux commands Tmux commands Vin commands Download today!

      How to get it:
      Complete and verifiable information is required in order to receive this offer. If you have previously made use of these free offers, you will not need to re-register. While supplies last! Please ensure you read the terms and conditions to claim this offer.

      >> Linux Cheat Sheet Bundle - Free download <<
      Offered by MakeUseOf, view their other free resources. Limited time offer.

      Not for you?
      That's OK, there are other free eBooks on offer you can check out here.

      Ivacy VPN - 5 years at 87% off NordVPN - 2 years at up to 68% off Private Internet Access VPN - subscriptions at up to 79% off Unlocator VPN or SmartDNS - unblock Geoblock with 7-day free trial Neowin Store for our preferred partners. Subscribe to Neowin - for $14 a year, or $28 a year for Ad-Free experience Giveaways: Polycade Home Arcade | $5K in cash | $10K in Crypto | Gaming Bundle Disable Sponsored posts · Neowin Deals · Free eBooks · Neowin Store

      Disclosure: A valid email address is required to fulfill your request. Complete and verifiable information is required in order to receive this offer. By submitting a request, your information is subject to TradePub.com's Privacy Policy.

    • By Abhay V
      AdDuplex: Windows 10 version 21H1 is now on over 26% of PCs, Windows 11 makes its debut
      by Abhay Venkatesh

      After a gap of a couple of months, AdDuplex has released its Windows version usage report for the month of July. The report is collected from 5,000 Microsoft Store apps that are running the AdDuplex SDK v.2 or higher, and around 60,000 Windows PCs were sampled for this report. This month’s highlight is the debut of Windows 11, which was formally announced in June. As for Windows 10, version 21H1 that was released in May is now running on over 26% of Windows machines.

      Just like the October 2020 Update, the Windows 10 May 2021 Update was an enablement package that light up new features in the OS. The underlying codebase for 21H1, however, is identical to versions 20H2 and 2004, meaning that the three most recent versions are serviced with the same cumulative updates. It is, therefore, not surprising to see that the rollout of the latest version has been faster than the previous versions has seen. This is only expected to increase as version 2004 begins to reach the end of support for consumer SKUs.

      With Windows 10 21H1 now on more than 26% of PCs, the three latest versions of the OS account for close to 88% of usage share. The title for the most famous version of Windows 10 is retained by version 20H2 at 36.3%, followed by version 2004 at 24.6%. Windows Insiders running Windows 11 in the Dev channel account for close to 1% of total devices.

      Windows 10 version 21H2 is also slated to be an enablement package. However, with Windows 11 expected to begin rolling out later this year, it will be interesting to see how the usage share changes, since there are still questions about the pace of the rollout and what the final hardware specifications will be.

    • By anmol112
      Hands-on with the new Microsoft Teams experience for Windows 11
      by Anmol Mehrotra



      Earlier this week, Microsoft released another Windows 11 build to Windows Insiders in the Dev Preview ring. The new build brought improvements to the UI as well as the new Microsoft Teams integration. Microsoft announced the Teams integration at the Windows 11 launch event last month. With the feature now rolling out to Windows Insiders, we decided to take a closer look at the new Teams integration for Windows 11.

      First time setup
      After you install the new Windows 11 build, you will see a Teams icon on the taskbar. Clicking on the option will open Team for the first-time setup. The setup is pretty simple.

      Microsoft allows you to use your regular MSA account for personal use. You can also use your work or school account if you have one and want it easily accessible.

      Once you select the account, Microsoft will ask you to verify ownership (if you have two-factor authentication) as well as add a phone number. This will add as a secondary username and also allow others to find you on Teams.

      Lastly, Microsoft will confirm the settings and ask you if you want to use your existing Outlook or Skype contact list to find people on Microsoft Teams. One thing to note here is that if you have used Windows Phone in the past or you use Outlook to sync your contacts then you will see your address book on Teams (provided you selected the sync Outlook contact list on the last step).

      Using the app
      The experience is same more or less. However, with a personal Teams account, users can now use it as way to stay connected to their loved ones. Moreover, you can now enter an email address to send a Teams message to them.

      This works in two parts: if the person already uses Teams, they will get a general chat notification. However, if the person you are messaging does not use Teams, they will get an email inviting them to join Teams and continue the chat.

      One thing that I personally believe can enhance the Teams experience is the support for SMS. While you can message people using phone numbers, they have to be in your contacts. Unfortunately, you can’t directly start a conversation with someone if they are not in your contacts. This is something that Microsoft can add in the future to allow users to start conversations by just entering the phone number of the person they want to talk to and if the person is not on Teams, they will get an invite to join the app.

      However, there is one way to invite others to a text chain and that is via the 'invite using link' option. As the name suggests, the option generates a custom link that can be shared with others to allow them to join a conversation.

      Lastly, Microsoft is also expected to merge the Meet Now feature into Teams in the feature. It will further enhance the user experience by allowing users to make audio and video calls using Microsoft Teams. Currently, the feature exists just as a placeholder button, but the company is expected to add it before Windows 11 is shipped as an update to existing Windows users.

      Do you plan to use Microsoft Teams on Windows 11? Let us know your thoughts below.

      For more information on Windows 11, you can check out our article on minimum system requirements as well as the list of CPUs that support Windows 11. Apart from the general requirements, Microsoft has also listed out specific feature requirements for Windows 11 including webcams, Bluetooth and Precision Touchpad on all upcoming laptops. Last month, Microsoft also updated the PC Health Check app to show why a device is not ineligible to receive the Windows 11 update. However, the company will allow some manufacturers to bypass the TPM 2.0 requirement and it is also allowing Windows Insiders with unsupported hardware to test Windows 11 Insider Builds. Several manufacturers have published a list of hardware that will be compatible with Windows 11.

      If you are still out of the loop, then you can check out hands-on video. If you want to get in-depth information about Windows 11 then you can check out our article covering all the new features and changes.

    • By anmol112
      How to fix Windows Hello not working in the latest Windows 11 build 22000.100
      by Anmol Mehrotra



      Yesterday, Microsoft released another Windows 11 build to Windows Insiders in the Dev Preview ring. The new build brought improvements to the UI as well as the new Microsoft Teams integration. However, it also came with a bunch of known issues, one of which was the broken Windows Hello.

      Fortunately, there is an easy fix for "Something went wrong" error when trying to use Windows Hello on Windows 11. If you are facing the issue, then you can follow the steps below to get the issue fixed:

      Click on Windows Search or the Windows button Type "Device Manager" and click on 'open'. You can also right-click on the Windows button and select Device Manager. Once Device Manager is opened, double-click on "Biometric devices" Now right-click on "Windows Hello Face Software Device" and click on 'uninstall device' Once done, reboot the system, let Windows download and install the latest drivers After the installation is finished, Windows Hello should be good to go. We hope Microsoft fixes this issue in the future build. While not critical, the issue certainly can be a pain for users who rely on Windows Hello to sign-in to their devices.

      For more information on Windows 11, you can check out our article on minimum system requirements as well as the list of CPUs that support Windows 11. Apart from the general requirements, Microsoft has also listed out specific feature requirements for Windows 11 including webcams, Bluetooth and Precision Touchpad on all upcoming laptops. Last month, Microsoft also updated the PC Health Check app to show why a device is not ineligible to receive the Windows 11 update. However, the company will allow some manufacturers to bypass the TPM 2.0 requirement and it is also allowing Windows Insiders with unsupported hardware to test Windows 11 Insider Builds. Several manufacturers have published a list of hardware that will be compatible with Windows 11.

      If you are still out of the loop, then you can check out hands-on video. If you want to get in-depth information about Windows 11 then you can check out our article covering all the new features and changes.

    • By Abhay V
      Here are the known issues in Windows 11 build 22000.100
      by Abhay Venkatesh

      Microsoft today rolled out Windows 11 build 22000.100 to Insiders running Dev channel builds. The cumulative update brings with it - among other things - improvements to the taskbar UI and the system tray, adding subtle design improvements, in line with the Windows 11 experience.

      The improvements include a better UI for the system tray, along with a new visual cue for when an app requires attention on the taskbar thanks to a background task. However, the ability to run Android apps, something that the firm announced during the Windows 11 unveil event, is yet to be added. When it does make it to the OS, it will happen through the Amazon Store that will be housed within the Microsoft Store.

      The firm isn't bringing any huge changes to the OS, as it is still addressing bugs and reliability concerns that are being reported by users running the Dev channel builds, while prepping the builds for the Beta channel. However, along with the list of bugs fixes, there are still a bunch of known issues that are being tracked. Here is the complete list of issues in Windows 11 build 22000.100:

      Issues such as the File Explorer bug might make it difficult for users to run apps reliably, so it is best to be aware of the problems before considering these builds for your daily driver. Additionally, there are some Windows Hello issues that have workarounds.

      Windows 11 build 22000.100 is rolling out via Windows Update to Dev channel users running the latest version of the OS. The release to the Beta channel should happen soon as the firm skipped releasing the latest 21H1 updates, citing the impending release of Windows 11 builds. Currently, there aren't any official ISOs available either for those hoping to perform a clean install of these builds.