Entering mapped drive letter in site setup

I'm having problems with library items not updating and in
reading earlier posts on the same subject someone suggested that
the problem could be resolved by mapping the shared drive to a
drive letter and putting the drive letter into the site setup. They
say that after doing that, the updates of library items will work
again.
I assume the mapped drive is put into the Remote Info/Remote
folder section of the site definition. Will this affect my
Contribute settings? And is a Recreate Site Cache recommended?

> Will this affect my Contribute settings?
is contribute used on this machine or on someone else's
machine??
And is a
> Recreate Site Cache recommended?
when you change the location of the Local Site Folder, the
site cache will
be rebuilt when you close the manage sites dialog box.

Similar Messages

  • Creating a symlink directory on a network share to a path below a mapped drive letter, local path, or UNC path does not work

    Am I correct in assuming I can not create a `symlinkd` to a network share, local path, or a UNC path on a network share that will be accessible by clients?
    ###Mapped drive letters don't work:
    1) navigate to a network share:
    pushd \\windows2008server\share\
    2) make a hardlink:
    mklink /d test_sharedir t:\directory\
    dir .\test_sharedir
    #Directory of Z:\test_sharedir
    #File Not Found
    UNC paths don't work:
    1) navigate to a network share:
    pushd \\windows2008server\share\
    2) make a symlink:
    mklink /d test_dirunc \\windows2008server\share
    dir .\test_dirunc
    #Directory of Z:\test_dirunc
    #File Not Found
    I can create a functional `symlinkd` on a local drive to a mapped drive letter or a UNC path.
    Are my assumptions above correct?
    We are in the middle of a migration and have created two symlinkd to UNC paths for shared DLLs, one below c:\windows\system32\ (directing to a share containing 64-bit DLLs) and one below c:\windows\syswow64 (directing to a share containing 32-bit DLLs).
    On the file server, we have had a path to 32-bit DLLs (from Windows 7 clients: s:\dll\).  I am attempting to rename this directory so that it is accessible via "s:\dll32\" and would like to create a symlinkd that links "s:\dll" to
    "s:\dll32" [again where S: is a mapped drive on a Windows 2008 server].  How do I do this?
    Thanks,
    Matt

    Hello Mandy,
    The link you sent me is for Netapp CIFS server daemon contained within DataOnTap (the Netapp OS) to follow symlinks.  I am inquiring about the Microsoft products Windows Server and Windows 7.
    To gain a better understanding of the Microsoft Windows Server and client (Windows) CIFS stacks and interaction of the stacks, I have referred to Figure 6 "Server Message Block Server Model" within the following (albeit older) document: http://download.microsoft.com/download/2/8/0/2800a518-7ac6-4aac-bd85-74d2c52e1ec6/tuning.doc
    You will see the following:
    I assume that the Windows Server CIFS server service must be "smart enough" to determine that a CIFS client is attempting access to a SYMLINKD and actually fill the request by following the SYMLINKD.  The CIFS server service does not appear
    to operate like this.
    1) Am I correct in my assumption that the CIFS client (redirector) and the CIFS server (server) do not following symbolic links (whether they be file or directory)?
    2) If not, how do I submit a feature request for this so that it can be reviewed and approved or not approved for inclusion/hotfix release?
    Thanks for your time,
    Matt Brown
    [UPDATE]
    Note that you can use a `directory junction` instead of using a SYMLINKD, to link to LOCAL resources (source). However, `directory junctions` do not allow access to resources over UNC.

  • Need Help Entering the Correct Data on Site Setup Window

    [DW CS5 on a Mac OS 10.7.5]
    I get an "FTP Error Message" after entering data on the Site Setup window after pressing Test.
    I want to upload to my host/server's cPanel one of a number of subdirectories that I have on my root directory. My first attempt at uploading the first subdirectory failed. Can someone help me determine which of my Site Setup entries is incorrect and what the correct entry ought to be?
    Perhaps I'm entering incorrect data in the "Root Directory" or Web URL" fields. My host server has given me the correct data, which I've carefully entered. Unfortunately, my testing on the Site Setup window continues to get this message: "An FTP error occurred — cannot open server folder /public_html/alaska/. Access denied. The file may not exist, or there could be a permission problem." Support staff at my host/server cannot determine why the uplaod attempts fail.
    I'll appreciate your guidance. Thanks, very much.

    Brett, thanks for your prompt e-reply.
    Unfortunately, removing the entry from DW's Root Directory field enabled a successful test, however, it caused all uploaded files to wind up in my very large root directory.     ( :-(      I had to do a lot of file management and deletions to clean up the root directory.
    My numerous approaches, after receiving your suggestion, appear to have found a successful workaround. Here's what worked:
    -- While in cPanel's File Management window, I selected the "/public_html" folder in the left column and clicked "New Folder" from the top toolbar. Once the new subdirectory folder was created, I went directly to the DW app where I then clicked the icon (atop and to the far right of the Files panel) subtitled "Expand to show local and remote sites".
    -- With DW's expanded window open, I selected the new folder name in the left half of the window. I then dragged and dropped all the files that were in the right-column's subdirectory's folder to the new folder in the left column.
    -- After completing the drag and drop effort, I checked cPanel's File Management window and verified that all files went to the appropriate subdirectory folder.
    -- Finally, I opened the site's pages online to see that all worked as intended.
    Over all, I wish DW were more reliable, such that when testing setups for *subdirectories* that have "/public_html" in the "Root Directory" field, they will *all* test successfully.
    Sadly, Adobe no longer supports CS5.    (  :-(
    Nevertheless, thanks for your assistance, Brett.

  • Warning when trying to launch application over mapped drive "We can't verify who created this file. Are you sure you want to run this file?"

    We have 2 load balanced application servers that map drives with programs on them for users from a central server that are giving the warning "We can't verify who created this file. Are you sure you want to run this file?". Basically how it works
    is a user logs in to one or the other application servers (for example, 10.0.0.1 or 10.0.0.2) and runs a log on script that maps an L:\ drive to the users folder on the central storage server (10.0.0.100). When the user goes to launch the .exe from the L:\
    drive it presents that warning.
    I've looked around and have seen recommendations that you need to add the site to the local intranet zone for IE, but when I try to add L:\ it tells me that I have entered an invalid sequence. It appears that you can only put network shares in that location,
    which is not how we're mapping the drive.
    Has anyone run in to this before and knows how to resolve it?
    Thanks!

    Hi,
    A mapped drive letter is not supported so please try to input \\server or \\server\folder to see if it will help. 
    If you have any feedback on our support, please send to [email protected]

  • DFS and Windows 7 x64 strange behavior when trying to access a DFS link through mapped drive

    I've manually mapped a network drive (Q Drive) to a DFS location. Whenever I go into "My Computer" and open the Q Drive it shows the DFS links but when I double click one of the links it randomly takes me back to the "My Computer" starting point showing my standard drive letters. If I click through the Q drive and the DFS several time it all of the sudden works. Sometimes this circle of clicking can go on for 5-10 times before it works properly.
    I'm running the x64 edition of Windows 7.  Any suggestions on how to make this work properly? Its very annoying.

    GPO mapped namespace where you can't connect through the mapped drive letter but can connect through the DFS UNC namespace? Do you use access based enumeration?
    I personally think it has something to do with network bandwidth, the security token and offline files. =)
    You can access the namespace itself but not any of the linked shares (try checking the ACL:s on the shares and you get permission denied, but you still see them, ie they are listed).
    I found a post sometime ago about corrupted/trunkated security tokens. If the member was part of too many AD groups the token was trunkated and corrupted. That was going to be my next move. Sniff the traffic and see what actually happens when the issue occur
    if theres something to be learnt there. Since it works correctly through the UNC adress but not through the drive letter you ough to be able to see what is different between the two requests.
    http://blogs.technet.com/b/askds/archive/2008/05/14/troubleshooting-kerberos-authentication-problems-name-resolution-issues.aspx
    One thing I noted was that it only happened to remotely connected computers on slow 3G connections (we use Direct Access). Never on LAN-connected computers with GB access or remote computers with fast (>15Mbps) access. We also use folder redirection,
    which I think could be part of the problem, ie the share never goes online, atleast for us the issue was itermittent, it never happend all of the time, just from time to time. And if I disconnected and reconnected it could fix the issue for that particular
    sessions, usually it didn't but occasionally it did (just pulling the network cable and put it back). Check the offline/online status the folders show up as offline even though they are online.
    Enough of my ramblings. Sorry to hear you still have the problem and I hope you find a way to solve it.

  • Mapped drives and linked graphics

    I have started a new position as a tech writer and have inherited files that will have to be maintained. As I am opening various files, I am finding a lot of broken links. As I investigate (by hovering over the file in the Links pallette), it appears that the basic file path is correct. But what I notice is that the drive letter on the broken ones is not the same. So for example, a link that works is Z:\Artwork\Product Name\filename.eps but a link that is broken is V:\Artwork\Product Name\filename.eps
    I also find some links that work, which link to the actual networked drive name instead of a mapped name, for example \\drivename\Artwork\Product Name\filename.eps
    If I try and link to a file myself, and then look at the path, it shows the path with the Mapped drive.
    So first of all, I assume that the broken links are caused by a user who did not map that drive to the same letter as was used by others. Is that correct? Second, how did someone create a link to the drive name instead of the mapped drive letter? Since I am going to have to fix these broken links, Since some of these files may also be used by the marketing folks, I would like to come up with an approach  so that anyone else opening the file will not encounter broken links, if they have not mapped the drives to the same letters.
    Thanks for your help.

    Well, either someone chose a different letter, or the drive letters were assigned from above by an IT department (and ordinary users are locked out of mapping new drives).
    It's possible to map the same share twice, if you have the power to do so. So just remap V: to the same network share as Z: and you're good to go, for your own purposes. I'm not sure how you could set it up to cover the rest of your question (so that anyone else opening the file would not get the missing links dialog) without relinking everything yourself. I suppose it'd be scriptable.

  • Replace Mapped Drives with UNC Paths via Group Policy Preferences

    We are currently using Group Policy Preferences to map network drives to drive letters for our users.  Given the risk of ransomware, etc. these days we want to provide users with a UNC link rather than a mapped drive letter.  Can anyone tell me
    the best way to do this?
    Thanks,
    Joe

    > We are currently using Group Policy Preferences to map network drives to
    > drive letters for our users.  Given the risk of ransomware, etc. these
    > days we want to provide users with a UNC link rather than a mapped drive
    > letter.  Can anyone tell me the best way to do this?
    Create shortcuts :)
    Martin
    Mal ein
    GUTES Buch über GPOs lesen?
    NO THEY ARE NOT EVIL, if you know what you are doing:
    Good or bad GPOs?
    And if IT bothers me - coke bottle design refreshment :))

  • Map a drive letter in a windows 2000 network

    I am a new mac user, trying to map a drive letter so I can connect to a windows network. How do I map a drive or otherwise get to the drive letter?

    Hi
    Your question would be better off in the Getting Online & Networking Forum:
    http://discussions.apple.com/forum.jspa?forumID=1222
    Steve

  • I had spilled soda on Mac keyboard the other day. Dried it as best I could , took battery out Nd hard drive. I let it sit for a little bit and turned it back on and I get a beeping sound. What do I need to do?

    I had spilled soda on Mac keyboard the other day. Dried it as best I could , took battery out Nd hard drive. I let it sit for a little bit and turned it back on and I get a beeping sound. What do I need to do?

    That isn't good.  The RAM is probably damaged, hopefully not the RAM slots.  This article explains why.
    Never leave food nor drink near your computer again.

  • When logging on to Windows 7 user gets a second mapped drive to the users home folder

    Morning,
    I'm working through an issue we've discovered whilst trialing Windows 7.  Our environment is setup as follows.
    Domain Controllers are Windows Server 2003
    Clients are Windows XP and Windows 7
    Windows XP and Windows 7 Clients are in seperate OU's
    All Windows XP Group Policies apply to Windows XP And Windows 7 clients, Windows 7 policies are then applied to Windows 7 clients after
    Windows 7 policies are setup such that any setting defined in a Windows XP Group policy is left unconfigured in the Windows 7 Group policy and only new Windows 7 settings have been set in Windows 7 Group Policies.
    We have users home folders mapped in their Account Directory account setting and set to H:\   to connect to
    \\domainname\dfs\home\username
    In addition we also as a fail safe map the drive via a login script using net use
    This has worked fine for years in windows XP, if Active Directory failed to map the drive for any reason then the login script would then map the home drive.
    In Windows 7 we have noticed a curious error.  We found after a period of a couple of weeks we suddenly started getting a new drive mapped.  This was identical to the H:\ drive mapping but was instead under drive Z:\.  In other words, the
    users home folder is mapped twice on h:\ and z:\.  This is not affecting any of the Windows XP users.
    I have gone through several logic reasons to ascertain why this has happened with the following findings.
    1. Originally we thought the error appeared when we tried out mapping the home drive using the mapped drives functionality new in Windows 7 group policy under preferences > windows settings > drive maps.  However, after forcing it to delete the
    Z:\ drive using this functionality we only succeeded in removing it with a group policy present to do it.  As soon as we removed that group policy the Z:\ drive came back
    2. Secondly i thought the reason we would be getting a z:\ drive when we haven't specified it anywhere is because active directory is trying to map to the H:\ Drive but it is already present therefore in Windows 7 it tries to map to a different drive. 
    Using Windows logic it tries the highest letter first which is unlikely to be in use i.e. z:\.  This makes sense because our logon script uses a net use h:\ command to map the drive and i believe by default these are set to perisistent.  Therefore
    the next time the user logs on H:\ is already mapped so the logic in Active Directory accounts maps the drive to Z:\ instead hence we end up with two mapped home drives.  To test this i altered the login script to set the drive maps to
    non persistent using persistent:no.  The logic here was that when the user logged off the drive would become unmapped so that when Active Directory tried to map the drive it would be able to use H:\.  Unfortunately this was not the case and
    Z:\ remains.
    3. Here is where i resolve the issue but i don't know why and is the bit i need answering.  If i go into my account on Active Directory and go to Profile and set the home folder drive letter to another letter i.e. change from H:\ to U:\,
    i get prompted to set full control etc and apply.  I then set the drive back from U:\ to H:\, again i am prompted for setting full control which i accept.  
    NOW when i login i no longer receive a Z:\ drive and only get an H:\ drive.  YAY, thats what i want, however, i do not understand why this is the case.  At first i thought it might be something in the active directory logic when i login to an XP
    machine and then login to a windows 7 machine.  IF you bear in mind that although i get a new profile in Windows 7 i still retain the same home folder setting.  However, after logging on an XP machine logging off then logging
    on a Windows 7 machine i still didn't get the Z:\ drive back. 
    I have tried creating a new user that ONLY receives our Windows 7 Group Policies and still they receive both an H:\ and a Z:\ drive which rules out the Windows XP policies conflicting with the Windows 7 policies.
    Does anyone have any ideas why i would get a second drive mapped to Z:\ logging into Windows 7 on a Windows Server 2003 domain? 
    Can anyone explain in more detail exactly how the Active Directory functionality works when you specify a connect to Drive letter for a users home folder?
    My current workaround is simply to add a net use command to remove the Z:\ drive.  I do not want to use Mapped Network drives using the new policy settings in Windows 7 RSAT because we have already found issues with it. 
    <input id="3daf20bf-4f4d-4a05-86da-2c30c205d580_attachments" type="hidden" />

    We had the exact same issue happen to us. No issue on Windows XP but Windows 7 mapped two home drives (F and Z). F was mapped during the login script and Z was being mapped by some unknown reason.
    We use Netapp for our storage and home drives and use a feature called CIFS Home Drive Mapping. This essentially maps a user to a folder not available through normal CIFS methods causing AD to error when setting the home drive. To get around this we use
    dsquery and dsmod to modify this attribute in the user account. This is the command we used...
    dsquery user -name %UserNameX% | dsmod user -hmdrv F -hmdir \\filer\$username$
    Notice there is no ":" after the F
    We determined the root causewas the value for the
    homeDrive attributefor the user account was set to "F" instead of "F:"
    When we updated our users to reference "F:" instead of "F" in their user, this problem was resolved.
    Use LDP or some other method to verify that the homeDrive attribute is set to "F:" (or any other letter) or you will have this issue.

  • Office 2013 Updates Error - Mapped Drive

    Event ID 11327
    Product: Microsoft Office Professional Plus 2013 -- Error 1327. Invalid Drive: V:\
    Event ID 1023:
    Product: Microsoft Office Professional Plus 2013 - Update 'Update for Microsoft Office 2013 (KB2956177) 32-Bit Edition' could not be installed. Error code 1603
    Error within Software Center: The software change returned error code 0x80070643.
    These errors only occur while updating through SCCM 2012 R2 automatic software updates. I can download the update directly from the Microsoft site and install without any errors. I am a new to SCCM, but was able to push out updates for Windows 7 and Office
    2010 without errors. After further testing I found that editing the Office 2013 install with the customization tool would allow the update to run. My MSP file custom install has "Remove Files" set to delete links on a mapped network drive (V:\).
    I am not sure how Office 2013 updates through SCCM (only) would care about a custom install portion that should be unrelated.
    I plan to exclude the V drive file removals from the custom install and just do it from a script. However, I am not sure what to do about updating the machines which currently have 2013 installed and constantly error while updating through SCCM.

    you are getting into different things here. Creating the ADR and runs every-time ? Microsoft do not release patches everyday and there is no point running the ADR everytime.coming to the question , how did you create and update the MSP for the Office Update
    file ? using ADR ,for deploying the updates,you will not have facility to control the command line options . for the drive letter issue (Product:
    Microsoft Office Professional Plus 2013 -- Error 1327), you can refer
    http://support.microsoft.com/en-us/kb/327763. you can try installing the MS office 2013 on a PC without any drive mappings and try the update. I suppose the issue could be with the drive mapping something related.
    Eswar Koneti | Configmgr blog:
    www.eskonr.com | Linkedin: Eswar Koneti
    | Twitter: Eskonr

  • PSE7 Restore to different PC fails to update drive letter in catalog

    I'm trying to simply copy my catalog and photos from my desktop to my laptop to have with me when I'm away. From all the discussions it seemed like backup/restore was the best method in order to preserve all the tags and other data associated with the images.
    Source Drive:
    Volume in drive H: is Data
    Volume Serial Number is 30AF-58D3
    Catalog: RH Main
    Picture Folder: h:\My Documents\My Pictures
    Catalog Folder: h:\My Documents\Adobe\Photoshop Elements\RH Main
    Backup Destination:
    Volume in drive M is OneTouch4 1-TB Serial number is e79a:bf54
    Now on the laptop I run the restore and choose 'Hard drive/Other Volume' and locate the Tally file on drive X: which is mapped to drive M on my desktop. It was simpler to restore across the network rather than moving drive M to the laptop.
    Under 'Restore Files and Catalogs to' I choose 'New Location', specify D:\, and check 'Restore Original Folder Structure'.
    On the laptop:
    Volume in drive D: is Apps_Data
    Volume Serial Number is 3069-7A44
    After the restore is complete, all of my photos are exactly where I expect them, D:\My Documents\My Pictures. The catalog is in D:\Catalog.
    The problem is that there are no thumbnails displayed for any of the photos. Examining the properties of each reveals that they are presumed to be on drive H: - their original location on my desktop.
    I could have easily copied the files myself, but I was counting on restore to do what I could not easily do - which was to update the database to reflect the correct location of the restored files. After all, restore PUT them there. Something must have convinced it that the drive letter containing the restored photos was still H:, but I'm at a loss as to how it could have come to that conclusion.
    Am I missing a step or am I expecting too much from backup/restore?

    The only drive visible to the laptop is X: which is mapped to M: on the desktop - the destination for the backup. The drive containing the original images on the desktop is H:.
    Automatically search and reconnect is checked.
    Update thumbnail doesn't work. Here's what's funny. Take a single example, a file named DSC_0005.JPG. I choose update and it starts scanning on D: and I can see it run through My Documents, My Pictures, and all of its subfolders. It turns out there are no less than 10 occurrences of that file name under My Pictures - each of them in a different sub-folder of course. So I let Update Thumbnail run and ended up at the reconnect screen where I can go find it manually. Why it didn't find any of those 10 files is a mystery. So I reconnected manually by browsing to the correct DSC_0005.JPG file - formerly at H:\My Documents\My Pictures\2009 01 01 but now on D: at the same path.
    Next I choose the thumbnail adjacent to it on the screen, DSC_0006.JPG. I check the rmf.3.cache file and the only entry in it is the folder that I just matched DSC_0005.JPG from - which is the same folder that contains DSC_0006.JPG. The process again runs for quite some time searching C: & D: for DSC_0006.JPG. Once again I'm presented with the Reconnect Missing Files dialog with no file suggested on the right side. So even with an entry in the cache pointing to D:\My Documents\My Pictures\2009 01 01, a folder containing a file named DSC_0006.JPG, it could not find a match!
    Back in PSE5 I had performed this reconnect on one file and then again on the rest as described on your web page and it worked as you described. So I'm familiar with that process but have not needed it lately, until now.
    The backup/restore functionality is so basic that I'm sure they tested it to some degree and it must work for some, otherwise many others would likely be griping. So there must be something unique to my setup that it's unable to come to grips with. Surely their internal testing of the restore feature included a test to restore to a different drive.
    Maybe they made the restore too smart. It certainly restores the file to the correct location based on the options I selected and the file retains its original name - but the database thinks it hasn't moved from the original location.

  • Group Policy Pref - Mapped Drives Not Applying to One User

    Hi All,
    I’m new to this list, so please excuse any etiquette slip ups.  
    I have three users at a site. All their machines are running Windows XP Service Pack 3 and have client side extensions installed. I created a group policy to map their default drives using GP User Preferences.
    Each of the drives is set to "update".
    As an example of the policy created XML is as follows:
    <Drive clsid="{935D1B74-9CB8-4e3c-9914-7DD559B7A417}" name="H:" status="H:"
    image="2" changed="2009-11-25 05:13:58"
    uid="{8A44D2F4-AAE5-4F43-AEEC-D36F08EA619C}" desc="Maps the users H drive to
    ServerName\users$\%username%" bypassErrors="1"><Properties action="U"
    thisDrive="NOCHANGE" allDrives="NOCHANGE" userName=""
    path="\\ServerName\users$\%username%" label="Home (ServerName)"
    persistent="1" useLetter="1" letter="H"/></Drive>
    and
    <Drive clsid="{935D1B74-9CB8-4e3c-9914-7DD559B7A417}" name="J:" status="J:"
    image="0" changed="2009-11-30 03:52:58"
    uid="{535CD462-A45D-4363-ADA1-2316D5ECC703}" desc="Maps J drive for users to
    \\ServerName\apps" bypassErrors="1"><Properties action="C"
    thisDrive="NOCHANGE" allDrives="NOCHANGE" userName=""
    path="\\ServerName\Apps" label="Apps (ServerName)" persistent="1"
    useLetter="1" letter="J"/></Drive>
    The group policy is applied to an OU for that site. 
    All three users are in the same OU.
    All three users are also in the same “xxsitecode Users” group.
    2 of the users log into their pc and get the mapped drives with no issue, but one user doesn’t.
    There are no other login scripts and the user has no manually mapped drives.
    He does have a H drive mapped using the profile field in his AD object as a temp measure. But every 90 mins any other manually mapped drives are removed by the policy.
    We don’t use roaming profiles
    To trouble shoot I have tried
    -    Reinstalling client side extensions
    -    Re-joining the pc to the domain
    -    Running gpupdate from the command prompt to see if any event logs are generated (none are)
    -    Manually mapping the drives to make sure there is network access etc – I can manually map them/he can access them.
    -    Creating the user a new account, when he logs in using that account he gets his mapped drives on all PC’s
    -    Getting the user to log into a different pc, when he does this he doesn’t get his drives – so it’s not his machine or profile
    -    Manually checking the security on the user object in AD against one of the users who gets their drives mapped
    I'm sure the GP is fine because it works for two other users and the testing isolates his user account as the issue.
    The Policy I’m having issues with is xxxx Mapped Drives/ Printers
    I have posted this issue on the tech net GP discussion groups page, but haven’t had any replies.
    Any suggestions would be appreciated.
    Simone

    What's interesting is that I applied a new GP to users - it has one policy setting and one preferences setting. He only gets the policy setting.. aka he gets the wallpaper but not the homepage.
    Also, Jorke asked me to post the gpresult /z .
    Microsoft (R) Windows (R) XP Operating System Group Policy Result tool v2.0
    Copyright (C) Microsoft Corp. 1981-2001
    Created On 10/02/2010 at 2:19:34 PM
    RSOP results for DOMAIN\USER on MACHINENAME : Logging Mode
    OS Type:                     Microsoft Windows XP Professional
    OS Configuration:            Member Workstation
    OS Version:                  5.1.2600
    Domain Name:                 DOMAIN
    Domain Type:                 Windows 2000
    Site Name:                   SITECODE
    Roaming Profile:            
    Local Profile:               C:\Documents and Settings\USER.DOMAIN
    Connected over a slow link?: No
    COMPUTER SETTINGS
        CN=MACHINENAME,OU=Laptops,OU=SITECODE,DC=DOMAIN,DC=com,DC=au
        Last time Group Policy was applied: 10/02/2010 at 1:06:38 PM
        Group Policy was applied from:      XXXXXADC.DOMAIN.com.au
        Group Policy slow link threshold:   500 kbps
        Applied Group Policy Objects
            Allow Remote Assistance
            au-mdwsus
            Default Domain Policy
            Legal Notice
            Proxy Settings
            Logon as service, operating system
            AU-WSUS
            Desktop Background & Home Page
            Reg Permissions for default desktop
            Local Admin & Local Power Users
        The following GPOs were not applied because they were filtered out
            SITECODE Mapped Drives/ Printers
                Filtering:  Not Applied (Empty)
            Local Group Policy
                Filtering:  Not Applied (Empty)
            AVD Rollout
                Filtering:  Disabled (GPO)
        The computer is a part of the following security groups:
            BUILTIN\Administrators
            Everyone
            Debugger Users
            BUILTIN\Users
            NT AUTHORITY\NETWORK
            NT AUTHORITY\Authenticated Users
            MACHINENAME$
            Domain Computers
            CERTSVC_DCOM_ACCESS
        Resultant Set Of Policies for Computer:
            Software Installations
                N/A
            Startup Scripts
                GPO: Desktop Background & Home Page
                    Name:         image.bat
                    Parameters:  
                    LastExecuted: 7:55:34 PM
                    Name:         swiftdesktop.vbs
                    Parameters:  
                    LastExecuted: 7:55:35 PM
            Shutdown Scripts
                N/A
            Account Policies
            Audit Policy
            User Rights
            Security Options
            Event Log Settings
            Restricted Groups
            System Services
            Registry Settings
            File System Settings
            Public Key Policies
                N/A
            Administrative Templates
                GPO: Allow Remote Assistance
                    Setting: Software\policies\Microsoft\Windows NT\Terminal Services
                    State:   Enabled
                GPO: AU-WSUS
                    Setting: Software\Policies\Microsoft\Windows\WindowsUpdate\AU
                    State:   Enabled
                GPO: Allow Remote Assistance
                    Setting: Software\policies\Microsoft\Windows NT\Terminal Services\RAUnsolicit
                    State:   Enabled
                GPO: Allow Remote Assistance
                    Setting: Software\policies\Microsoft\Windows NT\Terminal Services
                    State:   Enabled
                GPO: Allow Remote Assistance
                    Setting: Software\policies\Microsoft\Windows NT\Terminal Services\RAUnsolicit
                    State:   Enabled
                GPO: Allow Remote Assistance
                    Setting: Software\policies\Microsoft\WindowsFirewall\DomainProfile\GloballyOpenPorts
                    State:   Enabled
                GPO: Allow Remote Assistance
                    Setting: Software\policies\Microsoft\WindowsFirewall\DomainProfile\GloballyOpenPorts\List
                    State:   Enabled
                GPO: Allow Remote Assistance
                    Setting: Software\policies\Microsoft\WindowsFirewall\DomainProfile\AuthorizedApplications\List
                    State:   Enabled
                GPO: AU-WSUS
                    Setting: Software\Policies\Microsoft\Windows\WindowsUpdate\AU
                    State:   Enabled
                GPO: Allow Remote Assistance
                    Setting: Software\policies\Microsoft\Windows NT\Terminal Services\RAUnsolicit
                    State:   Enabled
                GPO: Allow Remote Assistance
                    Setting: Software\policies\Microsoft\WindowsFirewall\DomainProfile\AuthorizedApplications\List
                    State:   Enabled
                GPO: Allow Remote Assistance
                    Setting: Software\policies\Microsoft\Windows NT\Terminal Services\RAUnsolicit
                    State:   Enabled
                GPO: Allow Remote Assistance
                    Setting: Software\policies\Microsoft\Windows NT\Terminal Services\RAUnsolicit
                    State:   Enabled
                GPO: AU-WSUS
                    Setting: Software\Policies\Microsoft\Windows\WindowsUpdate\AU
                    State:   Enabled
                GPO: Allow Remote Assistance
                    Setting: Software\policies\Microsoft\Windows NT\Terminal Services
                    State:   Enabled
                GPO: au-mdwsus
                    Setting: Software\Policies\Microsoft\Windows\WindowsUpdate
                    State:   Enabled
                GPO: Allow Remote Assistance
                    Setting: Software\policies\Microsoft\Windows NT\Terminal Services\RAUnsolicit
                    State:   Enabled
                GPO: Allow Remote Assistance
                    Setting: Software\policies\Microsoft\Windows NT\Terminal Services\RAUnsolicit
                    State:   Enabled
                GPO: au-mdwsus
                    Setting: Software\Policies\Microsoft\Windows\WindowsUpdate\AU
                    State:   Enabled
                GPO: Allow Remote Assistance
                    Setting: Software\policies\Microsoft\Windows NT\CurrentVersion\Winlogon
                    State:   Enabled
                GPO: Allow Remote Assistance
                    Setting: Software\policies\Microsoft\Windows NT\Terminal Services
                    State:   Enabled
                GPO: Allow Remote Assistance
                    Setting: Software\policies\Microsoft\WindowsFirewall\DomainProfile\AuthorizedApplications\List
                    State:   Enabled
                GPO: AU-WSUS
                    Setting: Software\Policies\Microsoft\Windows\WindowsUpdate\AU
                    State:   Enabled
                GPO: Allow Remote Assistance
                    Setting: Software\policies\Microsoft\Windows NT\Terminal Services\RAUnsolicit
                    State:   Enabled
                GPO: Allow Remote Assistance
                    Setting: Software\policies\Microsoft\WindowsFirewall\DomainProfile\AuthorizedApplications
                    State:   Enabled
                GPO: AU-WSUS
                    Setting: Software\Policies\Microsoft\Windows\WindowsUpdate\AU
                    State:   Enabled
                GPO: au-mdwsus
                    Setting: Software\Policies\Microsoft\Windows\WindowsUpdate
                    State:   Enabled
                GPO: Allow Remote Assistance
                    Setting: Software\policies\Microsoft\Windows NT\Terminal Services
                    State:   Enabled
                GPO: Desktop Background & Home Page
                    Setting: Software\Policies\Microsoft\Internet Explorer\Security
                    State:   Enabled
                GPO: Allow Remote Assistance
                    Setting: Software\policies\Microsoft\Windows NT\Terminal Services
                    State:   Enabled
                GPO: AU-WSUS
                    Setting: Software\Policies\Microsoft\Windows\WindowsUpdate
                    State:   Enabled
                GPO: AU-WSUS
                    Setting: Software\Policies\Microsoft\Windows\WindowsUpdate\AU
                    State:   Enabled
                GPO: Allow Remote Assistance
                    Setting: Software\policies\Microsoft\Windows NT\Terminal Services\RAUnsolicit
                    State:   Enabled
                GPO: Allow Remote Assistance
                    Setting: Software\policies\Microsoft\WindowsFirewall\DomainProfile\AuthorizedApplications
                    State:   Enabled
                GPO: Allow Remote Assistance
                    Setting: Software\policies\Microsoft\WindowsFirewall\DomainProfile\RemoteAdminSettings
                    State:   Enabled
                GPO: Allow Remote Assistance
                    Setting: Software\policies\Microsoft\Windows NT\Terminal Services
                    State:   Enabled
                GPO: AU-WSUS
                    Setting: Software\Policies\Microsoft\Windows\WindowsUpdate\AU
                    State:   Enabled
                GPO: au-mdwsus
                    Setting: Software\Policies\Microsoft\Windows\WindowsUpdate
                    State:   Enabled
                GPO: AU-WSUS
                    Setting: Software\Policies\Microsoft\Windows\WindowsUpdate\AU
                    State:   Enabled
                GPO: Allow Remote Assistance
                    Setting: Software\policies\Microsoft\WindowsFirewall\DomainProfile\RemoteAdminSettings
                    State:   Enabled
                GPO: Allow Remote Assistance
                    Setting: Software\policies\Microsoft\Windows NT\Terminal Services\RAUnsolicit
                    State:   Enabled
                GPO: au-mdwsus
                    Setting: Software\Policies\Microsoft\Windows\WindowsUpdate
                    State:   Enabled
                GPO: Allow Remote Assistance
                    Setting: Software\policies\Microsoft\WindowsFirewall\DomainProfile\AuthorizedApplications\List
                    State:   Enabled
                GPO: Allow Remote Assistance
                    Setting: Software\policies\Microsoft\WindowsFirewall\DomainProfile\AuthorizedApplications\List
                    State:   Enabled
                GPO: Allow Remote Assistance
                    Setting: Software\policies\Microsoft\Windows NT\Terminal Services
                    State:   Enabled
    USER SETTINGS
        CN=Matthew Luhrs,OU=Users,OU=SITECODE,DC=DOMAIN,DC=com,DC=au
        Last time Group Policy was applied: 10/02/2010 at 1:54:53 PM
        Group Policy was applied from:      XXXXXADC.DOMAIN.com.au
        Group Policy slow link threshold:   500 kbps
        Applied Group Policy Objects
            Allow Remote Assistance
           **** SITECODE Mapped Drives/ Printers - has Gp Pref's that should apply
            Default Domain Policy
            Proxy Settings
            **** Desktop Background & Home Page - has Gp Pref's that should apply
            Local Admin & Local Power Users
        The following GPOs were not applied because they were filtered out
            AU-WSUS
                Filtering:  Not Applied (Empty)
            Legal Notice
                Filtering:  Disabled (GPO)
            Reg Permissions for default desktop
                Filtering:  Not Applied (Empty)
            Logon as service, operating system
                Filtering:  Not Applied (Empty)
            Local Group Policy
                Filtering:  Not Applied (Empty)
            au-mdwsus
                Filtering:  Not Applied (Empty)
            AVD Rollout
                Filtering:  Disabled (GPO)
        The user is a part of the following security groups:
            Domain Users
            Everyone
            Offer Remote Assistance Helpers
            BUILTIN\Administrators
            BUILTIN\Users
            NT AUTHORITY\INTERACTIVE
            NT AUTHORITY\Authenticated Users
            LOCAL
            Computer Account Operators
            Internet Users
            SITECODE Users
            DOMAIN-Public Folders Administrators
            All Email Users
            DOMAINSWIFTEMAIL
            Domain Admins
            Offer Remote Assistance Helpers
            WSUS Administrators
            DHCP Administrators
            CERTSVC_DCOM_ACCESS
        Resultant Set Of Policies for User:
            Software Installations
                N/A
            Public Key Policies
                N/A
            Administrative Templates
                N/A
            Folder Redirection
                N/A
            Internet Explorer Browser User Interface
                GPO: Proxy Settings
                    Large Animated Bitmap Name:      N/A
                    Large Custom Logo Bitmap Name:   N/A
                    Title BarText:                   N/A
                    UserAgent Text:                  N/A
                    Delete existing toolbar buttons: No
            Internet Explorer Connection
                HTTP Proxy Server:   Proxy:port
                Secure Proxy Server: Proxy:port
                FTP Proxy Server:    Proxy:port
                Gopher Proxy Server: Proxy:port
                Socks Proxy Server:  Proxy:port
                Auto Config Enable:  Yes
                Enable Proxy:        Yes
                Use same Proxy:      Yes
            Internet Explorer URLs
                GPO: Proxy Settings
                    Home page URL:           N/A
                    Search page URL:         N/A
                    Online support page URL: N/A
            Internet Explorer Security
                Always Viewable Sites:     N/A
                Password Override Enabled: False
                GPO: Proxy Settings
                    Import the current Content Ratings Settings:      No
                    Import the current Security Zones Settings:       No
                    Import current Authenticode Security Information: No
                    Enable trusted publisher lockdown:                No
            Internet Explorer Programs
                GPO: Proxy Settings
                    Import the current Program Settings: No

  • Mapped drive to other domain on another subnet disconnects

    Hi,
    I have a strange situation here. Tasked to change/upgrade nearly everything about this companies IT setup. Old servers, old domain name, old switches and some old workstations with XP. I bought all new servers, switches and some new workstations. set up
    all the new equipment and placed a linux box as a router between the two networks. Just for reference old is 192.168.1.0/24 and new is 10.1.1.1/24. I have the 10.1.1.0 network using DHCP and defining a static route to the 192.168.1.0 network as the router
    10.1.1.254. All seems to work fine and once I move a users network cable to the new switch and join them to the new domain. I can map a drive to the old file server's 1 big share and use other credentials as 'old domain\user' and password and all is well.
    The issue I am running into more and more is the mapped drive from the old network disconnects. A user will open a file and work on it and when they go to save it will say it is not available. They need to open the drive then save. On rare occasions they need
    to disconnect the drive and remap it.
    All of this was to try to buy some time while moving the users over one department at a time, but I am spending less time working and more time remapping drives.
    Any help would be welcome.
     

    Hi rcc9979,
    Seems like your map drive lose connection frequently, for good measure, please try to access or browse the mapped drive and wait for few minutes then see if it reconnects.
    And please let us know if this issue happens to all users, one Specific user or only some users in one network.
    Then you could use net use command with “/persistent:yes” parameter to map network drive then see if the issue still persists.
    If this happens to all users, this behavior might be caused by the systems can drop idle connections after a specified time-out period (by default, 15 minutes) to prevent wasting server resources on unused sessions.
    To fix this issue we could download fix tool or by Registry Editor
    More information please refer to:
    http://support.microsoft.com/kb/297684/en-us
    About net use command:
    http://technet.microsoft.com/zh-cn/library/bb490717.aspx
    Regards

  • Mapping drives from server core

    Hi,
    Is mapping drives drives from server core not supported? See the two commands below. One on the server with gui works fine and the one on server core does not.
    PS C:\Users\administrator.WBAD> New-PSDrive –Name W –PSProvider FileSystem -root \\192.168.1.101\HVBackup
    Name           Used (GB)     Free (GB) Provider      Root                                            
                                                                CurrentLocation
    W                                      FileSystem    \\192.168.1.101\HVBackup                      
    PS C:\Users\administrator.WBAD> Enter-PSSession hv1
    [hv1]: PS C:\Users\administrator.WBAD\Documents> New-PSDrive –Name W –PSProvider FileSystem -root \\192.168.1.101\HVBackup
    New-PSDrive : The specified drive root "\\192.168.1.101\HVBackup" either does not exist, or it is not a folder.
        + CategoryInfo          : ReadError: (W:PSDriveInfo) [New-PSDrive], IOException
        + FullyQualifiedErrorId : DriveRootError,Microsoft.PowerShell.Commands.NewPSDriveCommand
    Thanks in advance
    Will
    Will B

    Hi Will,
    You can use the command prompt command to map to a network drive. Please use the below command.
    net use <DriveName>: \\<RemotePath>\<Shared_drive_name> /persistent:yes /user:<username> *
    Let me know whether this works or not.
    Regards, Alan.

Maybe you are looking for