backup strategy in windows 7 - help me...
I have one Intel 520 120Gb SSD and one 1TB hdd for backup. For this scenario assume that ssd is full with data.
I want to have one backup set with "restore last version" functionality so user can restore his files them self. I can to this with windows backup utility. But, I want to have "restore last version" for last 30 days. So I need full backup one per month.
Second, I will use robocopy or disk2vhd to make backup by working days in separate folders.
Relative little data change over week. Maybe several Gb.
Questions:
1. How to prepare 1TB hdd for this scenario?
2. Do I have enough space for this?
3. How to configure windows backup for one per month full backup? Maybe I can use in some way space management option and let windows manage tracking version off files in the back as is possible?!...
Reply:
Hi foler, still needing help?
Read about Shadow Copies in this link:
Luiz Eduardo MCP Windows Server 2003. MCTS Network Windows Server 2008. MCTS Application Windows Server 2008. MCTS SQL Server 2008. Se a resposta ajudou, colabore com o Fórum e classifique.
------------------------------------
Reply:
Hello Foler, it helps you? Please, classify our reply. Thanks!Hi foler, still needing help?
Read about Shadow Copies in this link:
Luiz Eduardo MCP Windows Server 2003. MCTS Network Windows Server 2008. MCTS Application Windows Server 2008. MCTS SQL Server 2008. Se a resposta ajudou, colabore com o Fórum e classifique.
Luiz Eduardo MCP Windows Server 2003. MCTS Network Windows Server 2008. MCTS Application Windows Server 2008. MCTS SQL Server 2008. http://sqldicas.com.br - Se a resposta ajudou, colabore com o Fórum e classifique.
------------------------------------
Planned Hours are changing along with Actual in My Tasks
Hi Team,
Can any one please suggest me what setting should be made, for not to allow resources to change their planned hours in my task page.
My problem is when ever the resource enters actual hours against a project task, system is changing the planned hours automatically.
The tasks assigned to the resource are auto scheduled.
Please help, this is very critical for going live.
Awaiting your reply.
Thanks & Regards
Ravishankar Polepalli (MCP,MCC)
Microsoft Dynamics, Project Server and SharePoint Server Consultant
ravi.polepalli@gmail.com
Reply:
Ravishankar,
The system is acting as it is designed. You do want your "planned" hours updated based on the Actual/Remaining work input by team members, so that you have a realistic picture of what's happening.
If you want a unchanged record of what the "planned" hours were, then you need to have the Baseline Set.
Prasanna Adavi, PMP, MCTS http://thinkepm.blogspot.com
------------------------------------
Reply:
Hi Prasanna, Thanks for your reply.
Do you mean the Base line is mandatory to keep planned hours not changed when actual hours entered against a project task?
is there any other solution with out base lining the project plan?
Awaiting your reply.
Thanks & Regards
Ravishankar Polepalli (MCP,MCC)
Microsoft Dynamics, Project Server and SharePoint Server Consultant
ravi.polepalli@gmail.com
------------------------------------
Reply:
Sorry if I confused you.
Baseline is just a snapshot of what your planned hours/dates were, so that you can go back and compare actuals vs. baseline.
There is no way to prevent the changes to planned hours when actual information is input. That is the core of how ms project works and how it is different from ms excel.
Prasanna Adavi, PMP, MCTS http://thinkepm.blogspot.com
------------------------------------
Reply:
Please see the screen shot below, i have assigned this task with 8 hours. From the My Tasks page, i have updated the hours on Monday to 8 hours first and then to 5 hours. With that change, the work column also change to 5h and %work is 100% now. Actually it should be around 60% of it. Please suggest why this is changing as it should not.
Thanks & Regards
Ravishankar Polepalli (MCP,MCC)
Microsoft Dynamics, Project Server and SharePoint Server Consultant
ravi.polepalli@gmail.com
------------------------------------
Reply:
Hi Team,
Any one there to help me on this issue? This is very critical to move my project to production.
Awaiting your reply.
Thanks & Regards
Ravishankar Polepalli (MCP,MCC)
Microsoft Dynamics, Project Server and SharePoint Server Consultant
ravi.polepalli@gmail.com
------------------------------------
Reply:
Im not sure what to say here. If someone entered 5 hours on your 8 hour task and now it is saying it is 100% complete then they likely also entered a 0 in the Remaining work field.
That said it is 100% expected behavior that the 'Work' field will change if:
- the resource enters work and then sets the remaining work to 0. At this point the Work would be changed to equal the Actual Work field
- The resource enters Actual Work that is GREATER than the original Work value. So if your task was 8hrs and the resource enters 10 hours the Work field will now be 10hrs. If they entered 10 hours of Actual Work and edited Remaining Work to 5 then the Work value would be 15 hours.
Brian Kennemer - Project MVP
DeltaBahn Senior Architect
endlessly obsessing about Project Server…so that you don't have to.
Blog | Twitter | LinkedIn
------------------------------------
Reply:
Following Brian's note. From the screen shot, it looks like the resource also entered 0 hrours remaining, which leads to MS project recording the job as completed in less time then what was originally planned. I don't know if you are using the baseline as reference to track the original plan against actual work.
Muthu Krishnan
------------------------------------
Reply:
Hi,
That things you have mentioned are correct, if resource is entering manually 0 hours on the remaining work.
In my case, the system is changing them automatically.
Initially assigned a teask for 8 hours
Resource went and entered the actual as 6 hours
Resource again changed the actual from 6 to 8
and Resource again changed the actual from 8 to 4 (here is the problem). now system is changing the planned also to 4. It should not change it from 8 to 4.
Hope you understood my issue.
Thanks & Regards
Ravishankar Polepalli (MCP,MCC)
Microsoft Dynamics, Project Server and SharePoint Server Consultant
ravi.polepalli@gmail.com
------------------------------------
Reply:
Hi Ravi,
When you changed the actual work in My task page to 8 hrs, the % work complete changed to 100%. Now you again changed the hours to 5hrs and since the task is 100% complete whatever actual work you enter afterwards will be taken as actual work and the work will also update accordingly. But the task will remain 100%.
Workaround:
if you accidentally enter 8hrs actual in My Task page grid and if you want to change it to 5 hrs or any other value, do not directly enter 5hrs. First click on the task name for which you updated the actuals to 8 hrs.
The Edit details page will appear. Without making any changes, click on Back button. You will notice that the 8hrs is replaced by 0hrs in the My task timephased grid. Now enter the 5 hrs actuals for the specific date. You will get the desired result.
Thanks and Regards, Roopkumar Kamat (MCITP)
------------------------------------
Reply:
Hi All,
Thanks for all your replies. It helped me in understanding the system. But its too complex process to explain it to the end users as they are going to use this system.
What's your clients feedback/exp on using this task/timesheet functionalities!
Thanks & Regards
Ravishankar Polepalli (MCP,MCC)
Microsoft Dynamics, Project Server and SharePoint Server Consultant
ravi.polepalli@gmail.com
------------------------------------
BUG: Remote Desktop session is disconnected with protocol error if Remote Control is used on a Windows Server 2008-based computer
SYMPTOMS
When a user remote controls another user's session using Remote Desktop Services Manager or Terminal Services Manager on a Windows Server 2008-based computer, and then stops remote controlling, one or both sessions are disconnected with the following error:
Remote Desktop Disconnected
Because of a protocol error, this session will be disconnected. Please try connecting to the remote computer again.
CAUSE
This problem occurs if Remote Desktop Connection Client version 6.0.6001 or 6.0.6002 is used with the highest RDP Compression setting. Windows Server 2008 SP1/SP2 defaults to a lower RDP Compression setting, and thus will only exhibit the above symptoms if the setting has been changed to "Optimized to use less network bandwidth", which is the maximum. Windows Server 2008 R2 defaults to the maximum RDP Compression setting.
WORKAROUND
Change the RDP Compression setting on the server to "Balances memory and network bandwidth" (recommended) or "Optimized to use less memory" using Group Policy. If using Windows Server 2008 R2 you may also choose "Do not use an RDP compression algorithm". An alternative workaround is to use a different Remote Desktop Connection Client version than those mentioned above, however, this may not be practical. Below are instructions for making the change to the local group policy; if preferred you can use a domain group policy instead.
Windows Server 2008 R2
1. Logon to the Remote Desktop Services Session Host computer as an administrator
2. Start--Run gpedit.msc
3. In the left pane, under Computer Configuration, navigate to following:
Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Remote Session Environment
4. In the right pane, double-click on Set compression algorithm for RDP data
5. Select Enabled, and choose Balances memory and network bandwidth
6. Click OK to save the change
Windows Server 2008 (SP1 or SP2)
1. Logon to the Terminal Services computer as an administrator
2. Start--Run gpedit.msc, click Continue if prompted by UAC
3. In the left pane, under Computer Configuration, navigate to following:
Administrative Templates\Windows Components\Terminal Services\Terminal Server\Remote Session Environment
4. In the right pane, double-click on Set compression algorithm for RDP data
5. Select Enabled, and choose Balances memory and network bandwidth
6. Click OK to save the change
STEPS TO REPRODUCE
Windows Server 2008 R2 x64
1. Install 2008 R2 Standard (Full Installation) x64 from DVD using defaults
2. Upon first logon, scroll down the initial configuration tasks window and click on Enable Remote Desktop
3. Choose Allow connections from computers running any version of Remote Desktop (less secure), click OK
4. Open up Computer Management and create a test user, make them a member of the Remote Desktop Users group, on the Remote Control tab, uncheck "Require user's permission"
5. Connect from a PC using Remote Desktop Client version 6.0.6001 or 6.0.6002 to the server, logon as administrator
6. Connect from a PC using Remote Desktop Client version 6.0.6001 or 6.0.6002 to the server, logon as the test user
7. In the administrator's session, open up Remote Desktop Services Manager, right-click on the test user and choose Remote Control, click OK
8. After you are viewing the test user's desktop, press Ctrl-Tab to end the Remote Control
Windows Server 2008 x64
1. Install 2008 Standard (Full Installation) x64 from DVD using defaults
2. Upon first logon, scroll down the initial configuration tasks window and click on Enable Remote Desktop
3. Choose Allow connections from computers running any version of Remote Desktop (less secure), click OK
4. Open up Computer Management and create a test user, make them a member of the Remote Desktop Users group, on the Remote Control tab, uncheck "Require user's permission"
5. Change RDP Compression algorithm to "Optimized to use less network bandwidth" using instructions above
6. Connect from a PC using Remote Desktop Client version 6.0.6001 or 6.0.6002 to the server, logon as administrator
7. Connect from a PC using Remote Desktop Client version 6.0.6001 or 6.0.6002 to the server, logon as the test user
8. In the administrator's session, open up Terminal Services Manager, right-click on the test user and choose Remote Control, click OK
9. After you are viewing the test user's desktop, press Ctrl-Tab to end the Remote Control
NOTE: This problem may occur when connecting to a Windows Vista or Windows 7 host under similar conditions. I have not tested this theory, however.
As always I welcome your comments/questions/corrections/suggestions/etc.
Thank you for reading.
-TP
Reply:
version of mstsc on Win2003 server: 6.0.6000.16459
Version of mstsc on Win7 Desktop: 6.1.7600.16385
------------------------------------
Reply:
I am seeing this issue when RDP'ng from my Win7 desktop to a Windows 2003 TS. I can get into the TS just fine as administrator; however when I go to remote control a users session, I get kicked out of the TS with the protocol error.Same here.
version of mstsc on Win2003 server: 6.0.6000.16459
Version of mstsc on Win7 Desktop: 6.1.7600.16385
------------------------------------
Reply:
All,
I did some quick testing before when Defrag4 posted, and was unable to reproduce the issue. Questions:
1. If you disable compression in the .rdp file, does the problem still occur? To disable compression, open the .rdp file in notepad and modify the compression:i:1 to the following:
compression:i:0
2. You can run the 5.2.3790 version of the RD Client under Windows 7 as a potential workaround. I have it installed under XP in a separate folder, which I then copied to Windows 7. In this folder I only have two files:
mstsc.exe
mstscax.dll
If you do not want to have launch the 5.2.3790 exe each time you need to modify your .rdp file association, or you can add an additional option so that you when you right-click an .rdp file you can choose which version to use. This is not a long term solution, but it helps if you need it.
Thanks.
-TP
------------------------------------
Reply:
------------------------------------
Reply:
im having the same issue, it only happens when i remote control thin clients ( Axel Terminals), i can remote control sessions hosted on windows xp pc's without error.Same problem with my Win 7 Entreprise
it's impossible to remotely help my users on 2003 TS, it will crash with the "protocol error".
Connecting as admin is no problem though.
------------------------------------
Reply:
1. If you disable compression in the .rdp file, does the problem still occur? To disable compression, open the .rdp file in notepad and modify the compression:i:1 to the following:
compression:i:0
Hi TP,
I tried what you suggested but it did not work for me. I'm trying to connect to connect to a Remote Desktop Session using Terminal Services Manager. The screen pops up and I get a "Because of a protocol error, this session will be disconnected. Please try connecting to the remote computer again." (This is the same error I've been getting since making the switch to 7). I tried this with using the RD Gateway server set to Automatic and set to Do not use. Neither seems to work.
------------------------------------
Reply:
When I downgraded my mstsc client to an older version it works again, I think windows update might have replaced it because it started happening again, and i checked the version, sure enough it was the new RDP again.
------------------------------------
Reply:
Gold is for the mistress -- silver for the maid -- Copper for the craftsman cunning at his trade. "Good!" said the Baron, sitting in his hall, "But Iron -- Cold Iron -- is master of them all."
------------------------------------
Reply:
------------------------------------
Reply:
So only work around is to downgrade mstsc.exe on the Win08R2 server?
------------------------------------
Reply:
BWC-Dave: No. You would use the older mstsc.exe on the client PC.
-TP
------------------------------------
Reply:
Find a windows XP machine. Copy onto a USB pen drive (or something like that:
mstsc.exe
mstscax.dll
then create a subfolder called en-US and copy into it
mstsc.exe.mui
mstscax.dll.mui
Now copy these files onto your windows 7 machine. It doesn't matter where, so long as the en-US folder you've created follows it.
go into the properties of mstsc.exe and set the compatability options to windows xpsp3 and run as administrator
Now double click on mstsc. I've just tried remote controlling a user and it worked.
I'm now off to change my file associations to point at this older version of mstsc.exe
------------------------------------
Reply:
------------------------------------
Reply:
------------------------------------
Reply:
Workarounds:
1) use older client
2) RDP to an intermediary server and then RDP from there to your normal server. Remote control then works [for me].
For instance, if I RDP to TERM1 and remote control a session, I get the protocol error and disconnect. If I RDP to TERMTEST and then RDP from there to TERM1, then I can remote control just fine. A pain, but workable. The bigger problem is that I have support staff that I now have to explain how to use the old client.....
------------------------------------
Reply:
don't understand, this should be an easy fix for the guys works on this.
------------------------------------
Reply:
Client machine - Windows XP Pro
Terminal Server - Windows 2003
Symptoms - exactly as described. This isn't a Windows 7 issue, or a Windows 2008 issue. It is a BUG in the RDP client. When can we expect Microsoft to deliver a repaired RDP (MSTSC) program?
The sympotom appeared after a Microsoft Update - I guess that teaches me for accepting an update from a notoriously unreliable software company. I use Remote control nearly every day - someone on the terminal server needs something done.
Note - all of my Terminal Server users are running RDP sessions from Wyse V90 thin clients running Wyse WNOS software.
The "Work-around" in the article can not be applied - because the Registry Keys do not exist in Server 2003.
Adjusting settings on the client does not work - I ve changed them multiple times and get consistent errors - nothing that works.
Since my employees using Terminal Server are Geographically dispersed by hundreds of miles from here, I can't exactly stop by their desk to fix issues. This is a CRITICAL INCIDENT BUG that needs a HIGH PRIORITY patch.
------------------------------------
Reply:
Wyse recently posted a KB to address a problem with connecting WTOS devices to a terminal server. Can you take a look and see if this issue relates to you?
Go to www.wyse.com/manuals and search for KB 18695
Regards,
Christa
Christa Anderson [MSFT] Want the Windows Server 2008 Terminal Services Resource Kit? Click here.
------------------------------------
Reply:
I'm having the same problem when connecting to a TS server from a Windows 7 Ultimate can not do remote control in the User session, already ran all the alternatives overdimensioned this forum and not had success. Not content with that I called Microsoft support and they ended up talking trash saying that the problem could be in windows 2008 server and they do not support unless you have a support contract or want to pay for the hours of an engineer to resolve the issue.
This unfortunate situation!
------------------------------------
Reply:
Hi, Doc_M,
Wyse recently posted a KB to address a problem with connecting WTOS devices to a terminal server. Can you take a look and see if this issue relates to you?
Go to www.wyse.com/manuals and search for KB 18695
Regards,
Christa
Christa Anderson [MSFT] Want the Windows Server 2008 Terminal Services Resource Kit? Click here.
I did tested with some of my Wyse device it works fine
As for Windows to Windows RDPing ... i still can't do sh*t !!!!
------------------------------------
Reply:
ITs not operating system based issue, its an rdp update. in my case the update that caused the issue is KB969084. When uninstalled all my issues go away.
Just a pain that i have had to block what is potentiallly a useful update and that microsoft have yet to roll out a fix for this issue.
If anyone has a better way of resolving this other than uninstalling and blocking the update please let us know!
p.s for what its worth, i only get the issue controlling thin clients (axel terminals) too, PC base TS users dont cause me an issue..
------------------------------------
Reply:
------------------------------------
Reply:
I as well have the same issue as everyone above. Cannot remote shadow any of my terminal server users on Terminal Server 2003. This is a huge priority one issue. I cannot help any of my users. I also noticed I pushed out the new RDP 7 client to a few XP machines for testing and I cannot remote shadow from those machines either. So if you are using Microsoft XP do not update your RDP client otherwise you will no longer be able to remote shadow any of your terminal server users that connect via thin client. A huge problem microsoft has to release some patch for this to take care of this major issue.This info is not 100% correct; I solve the problem you are reporting in XP SP3 clients by updating to Remote Desktop Connection 7.0 client:
Description of the Remote Desktop Connection 7.0 client update for Remote Desktop Services (RDS) for Windows XP SP3, Windows Vista SP1, and Windows Vista SP2
http://support.microsoft.com/default.aspx?scid=kb;EN-US;969084#appliesto
There is also an update for Vista/2008 clients:
A terminal server session that is shadowed is incorrectly disconnected when the terminal server session that is shadowing stops shadowing on a computer that is running Windows Vista or Windows Server 2008
http://support.microsoft.com/default.aspx?scid=kb;EN-US;976110
I'll give some feedback about Win 7 asap
cheers,
------------------------------------
Reply:
amlopes that is not the problem I am reporting. The issue is after you do update your XP clients to the new RDP 7 protocol you can no longer remote shadow a WIN2003 terminal server connection created by a thin client. For example if I was an admin connecting to a terminal server via an XP machine with RDP 7 installed and I had to remote shadow one of my users on a thin client it will disconnect my session with an RDP protocol error. So upgrading XP clients to RDP7 puts them in the same boat as using Windows 7.
------------------------------------
Reply:
------------------------------------
Reply:
I am seeing this issue when RDP'ng from my Win7 desktop to a Windows 2003 TS. I can get into the TS just fine as administrator; however when I go to remote control a users session, I get kicked out of the TS with the protocol error.
version of mstsc on Win2003 server: 6.0.6000.16459
Version of mstsc on Win7 Desktop: 6.1.7600.16385
I am experiencing this exact same problem when remoting in from my Windows 7 Professional Retail 64 bit workstation to a Windows 32 bit 2003 Terminal server. The only way i can get this to work is to remote into one terminal server and from there remote in to the other one. Than it will work. This is really a pain when you have to do this all the time. Any fix for this from microsoft yet.
-Ian
------------------------------------
Reply:
------------------------------------
Reply:
I am getting the same thing under the following scenario:
1. 2008R2 server with RDS role on
2. Connecting from WinXP client
3. Join the WinXP session by domain Admin (defualt release of -cntl + [tab] accepted)
4. Joined session works fine, when release initiated, both session get the protocol error and both sessions are terminated.
Tried applying the GP of "balances memory and network bandwidth" and can't join a session at all.
Anyone know of any MS movement on this problem?
------------------------------------
Reply:
------------------------------------
Reply:
All,
Hm.. have been through everything here, but don't find anything that matches my situation which is:
Connecting to a Win 2008 standard server (virtual 32 bit) the remote user client gets disconnected when as administrator taking remote control "Your desktop connection is by the administrator....".
However this only happens when I connect from one of two Win7 ultimate. machines, and both of them are using the same mstsc. and mstscax. (ver. 6.1.7600.16385).
Thanks,
ASA-HP
------------------------------------
Reply:
------------------------------------
Reply:
same here : disable every experience checkboxes and it works fine. (on servers TSE 2K3, 2K8 & 2K8R2)
but an update from microsoft for MSTSC is required anyway, it's not a normal behavior to disable all the experience
------------------------------------
Reply:
------------------------------------
Reply:
I cannot beleive we let microsoft get away with this - there are two admins in our company both of which are using windows7 product and neither of us can administrate our own damn servers
I have tried unticking all of the options in experiance with no avail this just moves the problem to mouse clicking.
Have also tried to downgrade my RDP exe with no avail as win7 will not let me change the system32 folder
HAS ANYONE MANAGED TO FIX THIS ISSUE YET?
Thanks
------------------------------------
Reply:
Our workaround on win7 desktops is to use mstsc.exe version 6.0.6001.18000. In detail:
- a folder containing mstsc.exe (v.6.0.6001.18000) and mstscax.dll (v.6.0.6001.18266)
- a subfolder "de-DE" (or "en-US"... etc.) containing mstsc.exe.mui and mstscax.dll.mui
Running mstsc.exe out of that folder prevents disconnecting the session while shadowing another one on a terminal server.
Regards
Andi
------------------------------------
Reply:
Our workaround on win7 desktops is to use mstsc.exe version 6.0.6001.18000. In detail:
- a folder containing mstsc.exe (v.6.0.6001.18000) and mstscax.dll (v.6.0.6001.18266)
- a subfolder "de-DE" (or "en-US"... etc.) containing mstsc.exe.mui and mstscax.dll.mui
Running mstsc.exe out of that folder prevents disconnecting the session while shadowing another one on a terminal server.
Regards
Andi
I tried the above, and it still does not work.
On Windows 7 Premium 64, connecting to Server 2003 R2, try to shadow users on Wyse V10L. Get disconnected immediately.
Shadowing users on XP machines works fine, but as soon as I try to shadow someone on a Wyse, it disconnects me with the error message.
Microsoft really needs to fix this ASAP. It is seriously affecting my ability to support users.
------------------------------------
Reply:
Our workaround on win7 desktops is to use mstsc.exe version 6.0.6001.18000. In detail:
- a folder containing mstsc.exe (v.6.0.6001.18000) and mstscax.dll (v.6.0.6001.18266)
- a subfolder "de-DE" (or "en-US"... etc.) containing mstsc.exe.mui and mstscax.dll.mui
Running mstsc.exe out of that folder prevents disconnecting the session while shadowing another one on a terminal server.
Regards
Andi
I tried the above, and it still does not work.
On Windows 7 Premium 64, connecting to Server 2003 R2, try to shadow users on Wyse V10L. Get disconnected immediately.
Shadowing users on XP machines works fine, but as soon as I try to shadow someone on a Wyse, it disconnects me with the error message.
Microsoft really needs to fix this ASAP. It is seriously affecting my ability to support users.
It's a pity. It still works for me. Win7 Enterprise 32bit --> Server 2003 SP2 32bit --> Wyse S10
And I think the origin of the mstsc 6.0.6001 files was an 32bit XP pro.
------------------------------------
Reply:
Hi,
Wyse has a KB document that says to upgrade thin client OS firmware to at least 6.5.0_30 in order to fix this problem.
Search for 19555
Please see if updated firmware solves the issue for you.
Thanks.
-TP
------------------------------------
Reply:
I updated my Wyse V10L to the lastest OS stated above
I used the Wyse to connect to a 2003 R2 Terminal server
from my Windows 7 x86 machine i try to remote control to my test user which is connected to the TS
Got disconnect with protocol error...therefore problem is not fixed
------------------------------------
Reply:
------------------------------------
Reply:
Hi,
What is the KB number you are referring to? We would need to reference that when contacting Product support.
Thanks.
-TP
------------------------------------
Reply:
Hi,
What is the KB number you are referring to? We would need to reference that when contacting Product support.
Thanks.
-TP
exactly, because if you search, it doesnt exist !
------------------------------------
Reply:
Anybody already obtained and installed this hotfix?
Regards
Andi
------------------------------------
Reply:
After struggling with this issue, I have a clue as to what the problem is, which might lead all of you to resolution in this matter.
During our latest storm of protocol errors, I had two reusable sessions logged in on my Windows 2008 server. One was working, and one would consistently deliver a protocol error when minimizing/maximizing windows, especially those with large tracts of uniform color, e.g. white space.
After implementing the 'compression:i:0' fix in an RDP file on my Windows 7 (v.7600) client, the behavior was reversed: the session that was working, stopped working, and the session that was broken, started working.
This suggests the following:
In hour heterogeneous environment, desktop sessions may be opened and reopened via RDP by any number of administrators running different RDP clients, with different settings. It appears to me that each open session is tuned to the initiating client. Attempting to reopen an existing session with a different client MAY cause this problem. This is not 100% consistent, which leads me to believe that TS does attempt to tune the session to the client, but does not correctly do this for (perhaps) the compression settings.
This suggests why users who copy the XP RDP client onto their Windows 7 machines stop seeing the protocol error - because they have made the RDP clients uniform, and therefore all their logged-in sessions are 'compatible' when reopened by another user.
Most of our sessions are initiated by Windows 7 (v7600) clients, and protocol errors are few. I have been able to end our protocol error storms by logging off all sessions, and pre-opening and then disconnecting a number of sessions using the Windows 7 (v7600) client. These are then available for re-use by down-level RDP clients.
------------------------------------
Reply:
I have downloaded the patch on Windows 7 x64 and it works. I have not received an RDP error connecting to any of my TS sessions created by Wyse thin clients. Boy this was one long wait, now I do not have to rdp into one server then RDP into another just to shadow my clients anymore.
------------------------------------
Reply:
I've got this working finally!!! For anyone who's interested, this is what I did.This solution works perfect on any Win 7 machine (Professional or Ultimate 32 bit or 64 bit) using to remote into Terminal Server and attempting to remote control a user from there. I can't believe Microsoft has not come out with a fix. It seems as though this problem has been an issue for so long and it has not been addressed.
Find a windows XP machine. Copy onto a USB pen drive (or something like that:
mstsc.exe
mstscax.dll
then create a subfolder called en-US and copy into it
mstsc.exe.mui
mstscax.dll.mui
Now copy these files onto your windows 7 machine. It doesn't matter where, so long as the en-US folder you've created follows it.
go into the properties of mstsc.exe and set the compatability options to windows xpsp3 and run as administrator
Now double click on mstsc. I've just tried remote controlling a user and it worked.
I'm now off to change my file associations to point at this older version of mstsc.exe
Glen
------------------------------------
Reply:
The Hotfix is not needed anymore
Windows 2008 R2 Servicepack 1 is released and it looks like this fixes the problem.
We had the same problem using Wyse Clients for the user and Windows 7 Clients for the Admins connecting to Windows 2008 R2 RDS Server
after installing the SP1 on the 2008 R2 the problem was fixed
We did not install the SP1 on the Clients until now
Update: on Admin-Clients without Windows 7 SP1 you still need the Hotfix (sometimes) :)
------------------------------------
Reply:
------------------------------------
Reply:
MCITP: EA, EMA, VA; MCSA
------------------------------------
Reply:
as i wrote you need the SP1 on client and Server installed
else you have to install the hotfix http://support.microsoft.com/kb/2273487
we use thinclients from wyse with WyseOS 7 (Linux) and Windows 7 RTM Admin-Clients
after installing the SP1 on the server AND the admin-clients the problem was gone
------------------------------------
Reply:
I have a similar issue which will not seem to go away.
We have Server 2008 Standard (32 bit) running as a TS.
I use Win 7 64 Bit Pro - I have updated this to SP1
My issue is that before loading SP1 on the Win 7 PC I had the protocol error now and then.
Since SP1 whenever I try and shadow a user it just disconnects them. If I do the same on the Server 2003 users all works fine.
I have checked a bunch of things but this one has me screwed - I am nearly at the point where I need to remove Win 7 SP1 as at least I could shadow now and then.
Anyone with a clue as to what I should try next?
------------------------------------
Reply:
I'm in the exact same boat as flyingkiwi. I didn't have the problem until recently. I'm wondering if it is one of the hotfixes/windows updates that was released that caused this. I was fine for about 2 months. Now my users and I get the disconnect. They lose their work, and I get frustrated because I can't assist. Calling all MS guru's on this one!!!
JimPonder
------------------------------------
Reply:
I have this same problem.
- Server 2008 standard with SP2 running terminal service.
- When I shadow a user connected with an older version of mstsc I recieve "Because of a protocol error, this session will be disconnected. Please try connecting to the remote computer again."
I have also tried the "Work Around" suggested here and I still recieve the same error.
Is there somthing I am missing here?
------------------------------------
Reply:
Hi, flyingkiwi,
What you have seen is a bug we are aware of. In Win7 SP1 some new features are added to RDP but we need to fix something in Server 2008 side (Win7 server/Server 2008R2 already had the fix so it won't happen if you use them as terminal server) to make shadow works. A hotfix (for Server 2008) will be released soon to fix the issue.
Thanks.
------------------------------------
Reply:
------------------------------------
Reply:
Hi, flyingkiwi,
What you have seen is a bug we are aware of. In Win7 SP1 some new features are added to RDP but we need to fix something in Server 2008 side (Win7 server/Server 2008R2 already had the fix so it won't happen if you use them as terminal server) to make shadow works. A hotfix (for Server 2008) will be released soon to fix the issue.
Thanks.
I know that SP1 for Server 2008 R2 supposedly fixed this issue; I however still have this. Not just with R2, but also with one of my 2008 servers as well. Any news on this hotfix? Also is there anyone else out there still experiencing this? We have struggled with this for far too long.
------------------------------------
Reply:
I agree - its been going far far too long - even this thread was opened nearly 2 years ago!
The process we go through now is to use anything but Vista / Win 7 to RDP into our TS just to be able to assist users when shadowing them.
Seems crazy we refer back to old technology Windows XP for this to work correctly.
------------------------------------
Reply:
Psteve_uk,
I took what you explained above and put it all into a RAR file here: http://www.stevesig.net/test/Applications/RDP-XPSP3/RDP-XPSP3.rar
Thank you for your additional guidance on this.
-Steve Signorelli
- Edited by Steve Signorelli Friday, May 27, 2011 4:49 PM forgot to create proper link
------------------------------------
Reply:
Yes same problem.
However, I get no server errors and the user to be controlled gets disconnected.
XP mstsc.exe works fine.
Is there still no solution to this?????
Tom
------------------------------------
Reply:
Apparently it's THIS hotfix everyone is looking for.
http://thehotfixshare.net/board/index.php?showtopic=15195
I have NOT tried it yet. My work around was RDP to one terminal server.
Within the RDP session RDP to ANOTHER terminal server, and THEN remote control.
Because originally RDP to one terminal server and then remote control to user, DISCONNECTED USERS and I when remote controlling.
so RDP to terminal server and RDP WITHIN that terminal server to another term server and then remote works fine.
RDP>RDP within term serv>Remote=Works
RDP to term serv>Remote=Fails
------------------------------------
Reply:
------------------------------------
Reply:
Hello,
Confirmed hotfix http://support.microsoft.com/kb/2523307 It works. Please set mark as answer it.
Thank you,
Serkan
Microsoft bu servisi kullanıcılarına yardım etme, Microsoft ürünleri ve teknolojileriyle ilgili bilgi bankasını genişletme amacıyla ücretsiz sunmaktadır.
Bu içerik olduğu gibi benim tarafımdan hazırlanmış olup Microsoft tarafından herhangi gibi bir sorumluluk üstlenildiği anlamına gelmez.
Facebook Üzerinden Takip Et!
Twitter'da Takip Et!
------------------------------------
Reply:
Wish I could use this hotfix! I have tried all three of their files available (they all say Vista, despite the hotfix being for Server 2008; and yes I read the section that states that the files for 2008 are included in the installer). So as of now I'm still sitting unable to properly shadow my users.
Matt Cetlinski
------------------------------------
Reply:
------------------------------------
Reply:
I believe you need to have Server 2008 SP2 loaded on the server side - not just SP1
Windows 7 Sp1 is Ok
Try loading SP2 on your server and try it again.
------------------------------------
Reply:
Hi flyingkiwi,
Server 2008 and Server 2008 R2 are different.
SP2 for Server 2008 is not compatible with Server 2008 R2!
We have Server 2008 R2 and when I login with RDP from a Win7 client and another user logs in from an xp client and I remote control the xp-client RDP session and then quit remote controlling it then the xp client session on the Remote desktop host (= Terminalserver) gets disconnected - still to this day 15.Sept. 2011.
Sincerely
Andreas
Andreas
------------------------------------
Reply:
Hey everyone,
Like Andreas, I am still experiencing these errors.
I have both 2008 and 2008 R2 servers to support. The hotfix http://support.microsoft.com/kb/2523307 works great for windows 2008, but _not_ for 2008 R2. Even though the article specifies that the hotfix is for 2008 R2 / Windows 7, The "View and request hotfix downloads" button points you to the resources for Windows Vista and 2008. I tried downloading it onto a 2008 R2 server to install the hotfix and it would not run; the error indicated that it was not for this operating system.
<Rant> Come on, Microsoft, you can do better than that! It is sheer sloppiness! </Rant>
Montanageek
------------------------------------
Reply:
I am still having the issues as well. I have found a workaround that works sometimes, and with some clients. Wish I could nail it down to all of the time. One common theme however with the servers that have the issue persist regardless of what I do is that they are Server 2008 R2. If with the work around completed, the users only ever connect from one client then the issue is resolved. However if they move to another client (XP, or Win 7) the issue returns. I will continue to watch this thread as well as many others in the hopes that MS will one day perhaps redeem themselves and fix their broken product.
At one point I had a ticket open that made it into the Server development team (or so I was told after 2 months of work on it) and was informed that the issue occurs because there is an error that does not reach the surface that essentially reflects the error that we do see that does state the same, "Access Denied" when the failure occurs. At that point I was essentially told that I could begin working on getting a step by step procedure on how to reproduce the issue from step 1 of designing, configuring hardware, and installing the os all the way through to the point where I begin receiving the errors. After 2 months I had to throw in the towel as there were too many other issues to apply time to doing the work that Microsoft should be doing themselves.
Matt Cetlinski
------------------------------------
Reply:
I know one thing - it is doing my head in trying to shadow other users on TS 2008.
Its got to to stage where I have to use the VM XP to support them as using Win 7 Sp1 is an epic fail.
------------------------------------
Reply:
This is a bad koke from beginning to end.
My Scenario
Two New Dell Blades each running windows server 2008 R2 64 fully updated.
Each blade hosting two 2008 Svr 64 hosts
1 Guest is a Terminal server with 44 paid up liscences.
Another VM is an SQL 2008 server hosting a business critical com application used by the terminal servers.
Build is pretty far on and the CEO of the client who is pretty tech aware is on having a look - I go to shadow his session and it disconnects
(He has a new Dell laptop running 64 Windows 7 Pro fully updated, I am connecting in from a Win 7 64 bit.)
WHAT HAPPENS? He disconnects!
How whatever excuse for an MS employee who has been ignored this for two years rap you head around this:
I am your customer
That CEO is your customer
Dell is your customer
And you just made all three of us look like fools.
What we spend is what pays you.
So what about your glorious hotfix.
Well it's listed as VISTA. So I should just ignore that and install it on my 2008 servers?
After all it's not like at the stage of Microsofts decomposition into complete chaos and anarchy that anyone should actually believe KB/Hotfix descriptions. Like IT pros we will just keep using our psychic powers to keep second guessing around the completely disfuctional breakdown between MS dev and Support.
Fire someone, if it happens to be the same person that put Network Location Awareness in server products you will have done every single IT pro that spends money with MS a huge favor.
1)The issue was well documented here TWO YEARS ago. Changing local policy as decribed DOES NOTHING
------------------------------------
Reply:
Installed hotfix on the two 2008 64 machines....Windows6.0-KB976110-x64.msu
tried to install it on W7 64 bit laptop - result - not applicable to this computer.
Tested and it disconnected
Cleared off all sessions on 2008 64 terminal server and rebooted.
Tested and disconnected.
Fire someone. Fire them now.
------------------------------------
Reply:
I would agree. Fire someone! I am STILL dealing with this issue as well. I am continuing to chime in here because we HAVE to get someone with half a brain at Microsoft to get this resolved.
Matt Cetlinski
------------------------------------
Reply:
Not sure if it applies here, but we were getting this error on Remote Desktop for Administration connections to a specific server (using Windows 7 to 2003). Workaround was go to the properties Remote Desktop Connection > Experience > Allow the following and deselect all. Able to connect without error.
Hi all,
I tried to deselect all check-boxes on both sessions. It has no effect, still disconnecting.
Further more some other option that was helpful on another server when starting Task Manager for elevated rights check on the Processes tab the "Show processes from all users" check box. Try it, it might help.
In the meantime, hey Microsoft guys, we are paying a lot of money on the licenses, why do we have to pay more money to another software to do what embedded features in your soft is supposed to do? It worked on windows 2003, even on 2008 but for some reason it stopped working at one moment, it think it is a nasty update.
I have 4 TS's on 2008 32 bit and I need TeamViewer to remote connect in my own yard! Come on!!! This is outrageous!!! Please DO YOUR JOB!!!
Daniel Lupu
- Edited by Daniel Lupu Friday, January 20, 2012 7:58 AM
------------------------------------
Reply:
------------------------------------
Reply:
YEP. still a bug. Microsoft is probably one of the best at ignoring it's own partners, and customers that develop software for use on their OS's and with their own tools.
MICROSOFT > Please do something!
Matt Cetlinski
------------------------------------
Reply:
We're seeing this issue now as well.
Our environment: Terminal Servers either 2003 or 2008. Our end users connect to these terminal servers via thin client machines using RDP 5.5 or 6.0. I had previously connected to the same Terminal Servers our end users connect to using an XP 32 bit machine and RDP. No issues on that front.
Recently upgraded to a Windows 7 SP1 64 bit machine. Using RDP to connect to same Terminal Servers. Whenever I attempt to shadow an end user using Terminal Services Manager, if that end user is connected via RDP 5.5, the session will automatically disconnect and I never get the chance to shadow. When that end user is using RDP 6.0, we have no issues as long as that end user is on 2003 Terminal Server.
If that end user is on a 2008 Terminal Server, then the session will disconnect as soon as I attempt to shadow, no matter what RDP version they are using when connecting to one of our Terminal Servers.
------------------------------------
Reply:
Hi TP, i had the similar problem and i resolved with this KB publicated in March 2011 related Remote Desktop connections on Windows Server 2008 R2 post service pack 1.
The error message was:
Your remote desktop session has ended - The connection to the remote computer was lost, possibly due to.....
Install this KB and tell us if the problema was resolved:
http://www.microsoft.com/download/en/details.aspx?id=29169
Regards,
Heber Gonzalez
NOTA: Si llegaste a la solución de tu problema, por favor haz clic en "Proponer como respuesta" así otros visitantes del sitio pueden identificarlo como resuelto en caso de que les suceda lo mismo. Heber Gonzalez Consultor en Infraestructura y Mensajería Microsoft www.xelcon.com.ar http://ar.linkedin.com/in/hebergonzalez
------------------------------------
Reply:
Thanks Heber,
However this applies to Server 2008 R2 where I use Server 2008 Std. The bug remains..... :-(
------------------------------------
Reply:
Has anybody ever found a solution for this?? I still have a Windows Server 2008 32-bits with Service Pack 2 (so no R2), but I've tried every "solution" from this thread but without succes. The only workaround that works is installing Windows XP Mode and starting an RDP session to the server from that, but this is a time consuming option that I don't want. Plus it is not standard available on every PC in our company, so we first have to download it manually.
Why can't Microsoft find a solution for this after all these years??
------------------------------------
Reply:
Use remote desktop services manager, right click on the user your trying to control and click remote control. Change the key sequence to back out to Ctrl + *
After doing this one time its worked since then with any key sequence to back out of the remote control session.
------------------------------------
Reply:
Thank you, TP!
I never would have figured this out myself.
------------------------------------
Reply:
Hi,
I had came across with the similar issue of losing RDP connection post deployment of Service Pack 1 on Windows Server 2008 R2.
I managed to install the following windows Security Update for Windows Server 2008 R2 x64 Edition
KB2667402
Now, I together with other admins, can access via RDP simultaneously.
Cheers....
------------------------------------
Reply:
------------------------------------
Reply:
I have been facing the issues since long time as per Iqbal the patch KB2667402 works for me and RDP issues is now resolved
Thanks Iqbal for helping me in this:)
------------------------------------
Reply:
Seems the solution is fairly simple - limit the color depth to either 24 or 16 bit. Set this using GP. However, this is a workaround as the unwanted consequence is Aero features are disabled.
What I found:
1. RD session to Server 2008 R2 set to 32 bit and client connection (in this case a Win7 client) set to 32 bit - result, black screen on server, client disconnects with protocol error after using hot-key combination to exit.
2. RD session to Server 2008 R2 set to 32 bit and client connection set to 16 bit - result, can control, but exiting leaves the server connection unresponsive. Client is fine.
3. RD session to Server 2008 R2 set to 16 bit and client connection set to 16 bit - result, exits correctly. Client is fine.
I am no curious to discover whether the problem is depth or Aero, so will have to experiment more.
BTW - the above patch was already installed. Looking forward to further discussion! Thanks, Duckysan1
------------------------------------
Reply:
Hi,
Yesterday, I had came across with the similar issue of losing RDP connection post deployment of Service Pack 1 on Windows Server 2008 R2's cloned image.
I again managed to install the following windows Security Update for Windows Server 2008 R2 x64 Edition :
KB2667402
Now, I together with other admins, can access via RDP simultaneously.
Cheers again....
------------------------------------
Reply:
------------------------------------
Reply:
I have problem with remote control another users sessions (from WIN 7 to WIN XP) or (Windows 7 to Windows 7) on Windows Termilal Server 2008 SP2.
When I Install Windows 8 release 9200 ALL PROBLEMS WERE RESOLVED. And I NOTHING reconfigure on terminal server!
Now I can remote control RDP user sessions of Win XP, Win 7 and Win 8 Client from Win 8 RDP session on terminal server.
- Edited by Vlad Lerkin Friday, August 31, 2012 3:26 PM
------------------------------------
Web Analytic SP 2010 custom code
Microsoft.Office.Server.WebAnalytics
Microsoft.Office.Server.WebAnalytics.UI
There is a method called AnalyticsReportFunction which gets all of the data for us. This is the main code which get the data for us
Microsoft.Office.Server.WebAnalytics.Reporting.AnalyticsReportFunction a =
new Microsoft.Office.Server.WebAnalytics.Reporting.AnalyticsReportFunction();
foreach (AggregationLevel itm in Enum.GetValues(typeof(AggregationLevel)))
{
lstRepLevel.Items.Add(new ListItem(itm.ToString(), itm.ToString()));
}
foreach (ReportType itm in Enum.GetValues(typeof(ReportType)))
{
lstRepTypes.Items.Add(new ListItem(itm.ToString(), itm.ToString()));
}
object[,] res = a.GetWebAnalyticsReportData(TxtSiteUrl.Text, reportLevel,reportType,DateTime.Parse(txtFromDate.Text),
DateTime.Parse(txtToDate.Text));
WebException when browsing an entity
I get the "HTTPWebRequest_WebException_RemoteServer" error when browsing an entity. I found a few posts suggesting to:
- Verify Windows Authentication is enabled in IIS
- Extended Protection is set to 'Accept'
- Web.config is enhanced with an extra tag for <extendedProtectionPolicy policyEnforcement="Always" /> in the basicHTTPbinding tag
- reset IIS
however I'm still getting the same error. Any other tips/suggestions I should follow to troubleshoot this?
Javier Guillen
http://javierguillen.wordpress.com/
- Changed type Ed Price - MSFTMicrosoft employee Monday, January 19, 2015 7:45 AM
Buying Windows 7 off-the-shelf: Can it only be from a Microsoft Authorized Reseller?
Hello,
In my quest to make sure I'm not violating any clause of the Windows 7 EULA, I'm now led to questioning what are legitimate sources for purchasing the software.
In the EULA for Windows 7 Retail, in the "Transfer to a third party" section, it reads:
18. TRANSFER TO A THIRD PARTY. a. Software Other Than Windows Anytime Upgrade. The first user of the software may make a one time transfer of the software and this agreement, by transferring the original media, the certificate of authenticity, the product key and the proof of purchase directly to a third party. The first user must remove the software before transferring it separately from the computer. The first user may not retain any copies of the software. b. Windows Anytime Upgrade Software. You may transfer the software directly to a third party only with the licensed computer. You may not keep any copies of the software or any earlier edition. c. Other Requirements. Before any permitted transfer, the other party must agree that this agreement applies to the transfer and use of the software.
Now, it's the requirement of a "Proof of Purchase" in point (a) that leads me to question whether any ol' Joe can sell Windows 7 or not.
What measures are in place to differentiate between an original sale of the product and a sale between private parties?
I mean, obviously a big box retailer like Best Buy or Futureshop does not give you a copy of their proof-of-purchase when selling you a copy of Windows 7, because that's understood to be a retail sale and not a "transfer to a third party." But if Frank @ ABC Computers has a sealed copy of Windows 7 Pro that he's selling, how do I know I have to ask him to provide me HIS original proof-of-purchase or not? Is it a simple black-and-white distinction of either being an authorized reseller or not, or are there other criteria or qualifications? E.g. maybe all you have to be is a licensed business that buys from an authorized reseller, to be able to resell the product yourself?
I asked a few resellers on eBay that had tens of thousands of positive feedback and over 99% ratings whether they were Authorized Resellers or not. They all replied, "No." Am I missing something or are they missing something?
Any help and clarification would be much appreciated.
- Changed type Nicholas Li Monday, July 9, 2012 10:39 AM
Reply:
The first license holder can sell the right to use software (this particular copy) to another person.
Regards
Milos
------------------------------------
Reply:
But who's to say who is the first license holder? How do we know the first "seller" was or was not the first license holder? From the moment the retail package leaves the "factory", there has to be some way to qualify who falls on the seller side and who falls on the consumer side. Whether it's designations as an Authorized Distributor or Authorized Reseller or Microsoft Partner, something has to qualify that designation as a "seller". That's what I'm trying to understand here. From what you're saying, the first license holder would be the first consumer.The first license holder can sell the right to use software (this particular copy) to another person.
Regards
Milos
- Edited by waqqas31 Wednesday, June 13, 2012 8:49 PM Typos
------------------------------------
Reply:
------------------------------------
Reply:
Hi,
I fully understand that you have some concern about the EULA. However, this type issue should be supported via Customer Service. To contact Microsoft Customer Service and Support, telephone (800) MICROSOFT (642-7676). In Canada, call (877)568-2495.
Microsoft Customer Service hours of operation:
Monday through Friday, 5:00 AM - 9:00 PM Pacific Time
Saturday and Sunday, 6:00 AM – 3:00 PM Pacific Time
You can also contact Microsoft Support by email and chat, visit the following Microsoft Website for details:
Kim Zhou
TechNet Community Support
------------------------------------
Reply:
Hi Kim,
I contacted Customer Service and they were of little help. How can I contact someone in Microsoft's legal department so they can interpret these clauses of the EULA for me?
Thanks,
Waqqas
------------------------------------
Reply:
Hi Kim,
I contacted Customer Service and they were of little help. How can I contact someone in Microsoft's legal department so they can interpret these clauses of the EULA for me?
Thanks,
Waqqas
Anyone in the know on these forums?
------------------------------------
Update attribute does not trigger transition in for criteria-based membership sets
Hi guys,
I stumbled upon a scenario today which to me seemed a bit strange. So basically I have a set which is criteria based for, let's use first name (John). And then I have a MPR (Transition In) which triggers a workflow to send an email. Pretty simple scenario, right?
The thing that seems strange to me is that when I update a user to have first name John, the Transition In MPR is never triggered (not applied in the update to person request).
Is there a good explanation for this? Is there a way to achieve this goal?
- Changed type Markus VilcinskasMicrosoft employee Sunday, March 17, 2013 9:55 AM
Reply:
When you make the update, do you see the user added to the set?
If that set transition is happening - and as long as the set and workflows are correctly entered into MPR definition - this should work - there's not a lot to go wrong here - has to be something simple...
Frank C. Drewes III - Architect - Oxford Computer Group
------------------------------------
Reply:
Thanks Frank. One step closer :-)
What I am really trying to to is to do the same thing with custom attributes. I am trying to do the exact same thing using a custom boolean attribute, but no luck. The attribute is added to the "Administration: Administrators can read and update Users" MPR. Beyond that, I'm not sure what to do.
Thanks for the help!
------------------------------------
Populate Drop Down List inside a Repaeter
i have a drop down list (as one column/Item template) inside a repeater.....
how should i populate the same drop down list by fetching the contents from SPlist?
i know the LINQ query used to fetch the items but how to bind this with control inside repeater
Reply:
Hi, In the Repeater ItemDatabound event add following code
if (e.Item.ItemType == ListItemType.Item || e.Item.ItemType == ListItemType.AlternatingItem) { ((DropDownList)e.Item.FindControl("dropDown")).DataSource =(DataRowView) e.Item.DataItem;//Or any other datasource. ((DropDownList)e.Item.FindControl("fropDown")).DataBind; } Thanks
Satyam MCITP, MCPD
------------------------------------
Reply:
Hi,
Use itemDataBound event like this
protected void repeater_ItemDataBound(object sender, RepeaterItemEventArgs e)
{
DropDownList ddlList= (DropDownList)e.item.findcontrol("dropdownid"); //lookup for your item
ddlList.DataSource = SPList datasourceName;
ddlList.DataBind();
ddlList.DataValueText = "Name";
ddlList.DataValueField = "ID";
}
Thanks
Selva.R
------------------------------------
Reply:
Thanx for the reply @satyam and @Selva......
How to update the Splist item.........
Based on the selection made from drop down list in repeater....i need to update the contents of SPlist using LINQ query....
how to get the unique id of each row...as drop down list is present in every row....
------------------------------------
Reply:
Are you using SPMetal for saving and updating list?
Do you have save or update button every row in the repeater ctrl?
If yes, change it as below,
add in you design
OnItemCommand="OnItemCommand">
<asp:Button ID="Update" runat="server" CommandName="Update" />
then use OnItemCommand
protected void OnItemCommand(object source, RepeaterCommandEventArgs e)
{
if(e.CommandName == "save")
{
dropdownlist ctrl = (dropdownlist)e.Item.FindControl(drdname)
if(!string.isNullEmpty(ctrl.selectedItem.value))
list[0]=ctrl.selectedItem.value
}
Repeater1.DataSource = list;
Repeater1.DataBind();
}
Thanks
Selva.R
- Edited by Selva R Thursday, August 30, 2012 7:36 AM
------------------------------------
Reply:
No i am not using SPMetal for saving and updating list.
No i don't have save or update button every row in the repeater ctrl.
I want the item present in one particular column of SPlist to be changed/updated on select of value from drop down list....
------------------------------------
Reply:
Hi,
Using selectedIndexchanged, you can update the column of the repeater.
I dont understand your exact requirement. I dont think without using spmetal we cant update items to the list...
Below code might be helpful..
protected void ddlList_SelectedIndexChanged(object sender, EventArgs e)
{
var ddl = (DropDownList)sender;
// var lbl = (Label)ddlList.FindControl("lbldummy");
//lbl.Text = ddlList.SelectedValue;
var ri = (RepeaterItem)ddlSizes.Parent ;
var lbl = (Label)ri.FindControl("lbldummy");
lbl.Text = ddlList.SelectedValue;
}
<asp:Repeater ID="rep" runat="server">
<ItemTemplate>
<asp:DropDownList ID="ddlSizes" runat="server" AutoPostBack="True" OnSelectedIndexChanged="ddlList_SelectedIndexChanged">
Thanks,
Selva.R
- Edited by Selva R Thursday, August 30, 2012 12:04 PM
------------------------------------
Reply:
Due to some change in the req i have to use Discussion board list...
i have created one discussion board list
i have a drop down list inside repeater....on select of this item from drop down list the item in column of the list should be updated ........
------------------------------------
Reply:
public
void ddlList_SelectedIndexChanged(object sender, EventArgs e)
{
var ddl = (DropDownList)sender;
var ri = (RepeaterItem)ddl.Parent;
SPSite mySite = SPContext.Current.Web.Site;
SPWeb myWeb = mySite.OpenWeb();
SPList listb = null;
//SPListItemCollection items = listb.Items;
using (SPWeb currentWeb = new SPSite(SPContext.Current.Web.Url).OpenWeb())
{
currentWeb.AllowUnsafeUpdates =
true;
listb = currentWeb.Lists[
"PostIdeaDB"];
currentWeb.AllowUnsafeUpdates =
false;
}
//myWeb.AllowUnsafeUpdates = false;
foreach (SPListItem listRecords in listb.Items)
{
if (listRecords["AssignStage"].ToString().Equals("Posted"))
{
//listb.Folders.Add();
listRecords[
"AssignStage"] = ddl.SelectedValue.ToString();
listRecords.Update();
}
}
myWeb.AllowUnsafeUpdates =
true;
}
<
asp:DropDownList ID="ddl" runat="server" AutoPostBack="true" OnSelectedIndexChanged="ddlList_SelectedIndexChanged"></asp:DropDownList>list item not getting updated
------------------------------------
Reply:
Hi,
try{
SPSecurity.RunWithElevatedPrivileges(delegate(){
currentWeb.AllowUnsafeUpdates = true;
--- Add your code here
}
}catch(SPException ex)
{
}finally{
currentWeb.AllowUnsafeUpdates = false;
}
Selva.R
- Edited by Selva R Friday, August 31, 2012 1:15 PM
------------------------------------
FPSMC failed to download engine
New install of FPSMC 11.1.1614.0 on a standalone server and forefront protection for exchange 11.0.677.0 on 3 new Exchange servers.
The agent deployed to the servers fine. Created a simple job to update the servers and it fails everytime, this is the message and only error I see:
Also what are the latest build numbers and what should I be on?
Job Name: Update Servers
Job Type: Redistribution
Success: false
Completed: 30 August 2012 00:00:03
Engine(s) downloaded
Command,Kaspersky,Microsoft,Norman,VBuster,WormList
Source
http://forefrontdl.microsoft.com/server/scanengineupdate
Message(s)
Diagnostics Messages
Reply:
Hi,
Thank you for the post.
FPSMC downloads engines on the schedule that you specify when you create a signature redistribution job. It only downloads signatures when you create a job and you specify when and how often it does so. If you find that some of your engines are not updating, you should manually run a Signature Redistribution job that targets the managed servers with the out-of-date engines
Regards,
Nick Gu - MSFT
------------------------------------
Reply:
Its the signature redistribution job that is failing (every time). I have it scheduled twice a day, I have also ran it manually it always fails. The internet access is locked down pretty tight on our servers but it dosnt give me any useful error to see why its failing - Success = false is all I get.
I downloaded a powershell script http://support.microsoft.com/kb/2292741 that gets the updates from the same place:
http://forefrontdl.microsoft.com/server/scanengineupdate and that works so I know it can get there. I am thinking of scheduling that to run everyday and having the servers get the updates by url but that dosnt seem like the best solution.
------------------------------------
Problems with PXE-boot
I got the PXE-E53 no filenname....
When I follow the SMSPXE.log I see this "error"
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777534" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
Where the ItemKey is a key already used by another computer. If I delete all computers from my "Windows 7 Collection" the PXE booting works like a charm. So im pretty much stuck here.
It must be something with the resource id´s. Because it works as I said when I delete all the computers and all the recource id´s are deleted with the computers.
(I see no errors in my distmgr)
Anyone else seen this problem and can help me to solve it?
- Moved by Joyce Wang [MSFT]Microsoft employee Friday, August 31, 2012 5:08 PM (From:Configuration Manager 2012 - General)
Reply:
Torsten Meringer | http://www.mssccmfaq.de
------------------------------------
Reply:
Tracing that log now when I trying to PXE boot a computer, but nothing happens at that log, and I got the same errors in SMSPXE.log
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777550" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
And when Im searching for that itemkey, I got an answer that it belongs to another computer HOP-J2 with another MAC-address 40:61:86:8E:53:1E and the one I trying to install have 40:61:86:8E:53:48.
Any other log I can check? Its so strange
- Edited by Marcus Wessberg Wednesday, August 29, 2012 6:16 PM
------------------------------------
Reply:
Check "Computers that may share the same SMS Unique ID" report?
How you deploy Windows 7? did you use image ? if yes.... did you sysprep machine to make sure that you reset GUID? or did you include CCM client agent with image before capture?
Abduljalil Abolzahab
------------------------------------
Reply:
Reset the GUID? (had this problem also then).
Yes I included the agent, but I have deployed the machines I have now from another deployment server, which I want to get rid off.
Okey I check that report tomorrow. Thank you for the advice
------------------------------------
Reply:
------------------------------------
Reply:
------------------------------------
Reply:
Check "Computers that may share the same SMS Unique ID" report?
Runned this, and there was no computers with the same unique ID.
This is so strange, what I miss here?
------------------------------------
Reply:
Abduljalil Abolzahab
------------------------------------
Reply:
I tried to PXE boot a virtual machine, and it worked like a charm.
------------------------------------
Reply:
Install the following tool, it's integrated with SCCM, then right click on collection that contain computer with shared GUID -> ConfigMgr Collection Tools -> Generate New GUID
http://myitforum.com/cs2/blogs/rhouchins/0401ConfigMgrTools.zip
Good Luck
Abduljalil Abolzahab
------------------------------------
Reply:
Not working for SCCM2012? Nothing happends, and cant se the configmgr collection tools
------------------------------------
Reply:
------------------------------------
Reply:
Hi,
This is for SMS 2003 but you can check how to reset GUID, you can check for your reference:
Managing Duplicate Microsoft Systems Management Server Unique Identifiers
Abduljalil Abolzahab
------------------------------------
How to add dropdown in content editor ribbon in sharepoint 2010
- Edited by Ashok Chintaman Patil Monday, September 3, 2012 3:38 PM convert to type
Computer Certificate Not being Autoenrolled (2008 R2 GOP to Win 7)
Hi
We have a GPO created to auto-enroll the computer certificate, however it does not seem to work.
Running a GPRESULT /R shows the policy being deployed.
This is on Windows 2008 R2 deployed to Win 7 machines
Is there something obvious missing ?
Thanks
Reply:
My weblog: http://en-us.sysadmins.lv
PowerShell PKI Module: http://pspki.codeplex.com
Windows PKI reference: on TechNet wiki
------------------------------------
Reply:
Hi
I did create another cert from the template (v3) and enabled autoenroll. But I have noticed that when you go through the mini wizard to autoenrol a cert in GPO it only gives the standard certificates to publish (computer, Domain Controller, IPSEC) but no templates are available.
I have another setup using the standard computer certificate and this autoenrolls fine from AD.
Any thoughts?
Thanks
------------------------------------
Excel Web Apps not giving PRINT option in SharePoint 2010
Hi All,
First of all like to congratulate to build a wonderful product named SharePoint 2010, and equally appreciated Office Web Apps.
Recently we purchased Office Web Apps to enable the PRINT option in Excel document open in SharePoint 2010 web site. Initially we are not able to find the PRINT option at all in Excel. We thought there must be some patch or service pack which can resolve the issue. So we installed the latest service pack 1 but still not able to find the option.
Then we followed the same article by going through which we decided to purchased Office Web Apps software as shown below:
http://office.microsoft.com/en-us/web-apps-help/print-a-document-in-office-web-apps-HA101812661.aspx
We carefully gone through the document and not able to understand where we went wrong. Because the article clearly showing that "If you don't able to find Print command in SharePoint" , for "if" we meant that by default the print option is always avialable with Excel Web Apps in SharePoint 2010 but sometime if it may not apeear then we need to follow the browser print options.
Then we dig down to official Office sites where we got to know that the option will be available with SkyDrive. The solution which is not preferred by one of our clients, since the excel document are too sensitive to be deployed in some other space.
Hence our question is:
1) Is there any ways to enable the PRINT option to be available from SharePoint 2010 in Excel Web Apps without going to SkyDrive option?
Please provide any kind of solution which can help us print Excel sheet from sharepoint 2010.
With High Regards to all the team members in Microsoft,
Neeraj Baluni
- Edited by Nbaluni Friday, August 31, 2012 7:40 AM removing my personal email ID
Reply:
Hello,
use ctrl+p!
Print a document using OWA:
Daniel Bugday
Microsoft Community Contributor, Member of Microsoft Extended Expert Team, MCT, MCTS/MCPD SharePoint 2007/2010, SQL MCDBA, MCSE
Blog: SharePoint By Bugday
Twitter: Follow me on Twitter
Technet: My Ask The Expert Area On Technet
Founder of SharePoint Forum
------------------------------------
Reply:
Hi Daniel,
Thanks for the reply. CTRL+P opens the print from browser window option, which I already mentioned is known and not feasible for us.
We want to have print option in Excel Web Apps from SharePoint 2010. Is it possible ?
Regards,
NB
Neeraj Baluni Principal
------------------------------------
Mircrosoft 2010
Reply:
Generally speaking, we don't need to pay for the trials, so I'm not sure what exactly you've bought.
And, if it indeed is a trial, it cannot be reinstalled after the trial has expired.
You may consider to convert your trial to a full-product version by follow the directions in the following link:
http://office.microsoft.com/en-us/buy/convert-your-trial-to-a-full-product-version-HA101812668.aspx
Or, you may consider the Office Customer Preview:
http://office.microsoft.com/en-us/
Max Meng
TechNet Community Support
------------------------------------
Setting Two IP adress in windows 7 ultimate pc
Dear Sir
When I am adding two ip adressess in one pc one is 192.168.1.2 & another is 172.25.39.5 (Local Router Ip address) . After addition of two networks internet is properly not working means some sites are working & some sites are not working like facebook, Gmail,Yahoo mail, so please guide me .
Reply:
Is that two NICs or two IPs on one NIC? What is the default gateway setting? (You can only have one per machine, not one per NIC).
Bill
------------------------------------
Reply:
Can you type ipconfig /all and post the output here?
Possible reason for specific sites not working are:
- Name resolution problem (Solution: Manually set DNS to 8.8.8.8)
- Browser issue (Solution: Install an alternative browser and check again)
- Restrictions on local computer (Solution: Check for settings in hosts file: %windir%\drivers\etc\hosts , parental control systems or other restrictions on the computer)
- Problems with the router, unlikely though (Solution: Factory reset the router)
Jaap Brasser
http://www.jaapbrasser.com
------------------------------------
Reply:
Hi,
Please double check your default gateway settings and DNS settings.
You could also refer to this thread: How to assign different/multiple IP address to NIC network card
Regards,
Vincent Wang
TechNet Community Support
------------------------------------
Reply:
Hi
You haven't mentioned the netmask ... if you set this wrongly then it could cause the problem you described.
You should set:
192.168.1.2 & netmask 255.255.0.0
172.25.39.5 & netmask 255.240.0.0
see http://en.wikipedia.org/wiki/IP_Addressing#IPv4_private_addresses
Regards
Luke------------------------------------
Windows server 2008 r2 enterprise X64
HI Gurus,
I am in big trouble and seeking the solution.
My friend has installed a windows server 208 r2 enterprise x64. two days back i uninstalled one software and there was a abrupt power shut down. now my system is not reboting again. nither in normal or safe mode.
some of the actions i did:
1.i downloaded the windows server 2008 r2 and made the bootable drive and tried to repair, the system says that it can not repair as operation system version is mismatching.
2.also i took back up vhd file of operating sysem well before the system crashed , now i am using that backup to restore the system back but system fails to do so and throwing same erorr as OS version is mismatching.
3.now i have downloaded many windows server 2008 r2 with different versions but i am really cant figured out which one is actually required .
4.while booting with bootable dvd , in command prompt i have used command "ver" to know the version..it is showing version 6.1.7600. now my doubt , is that version is of bootable dvd's operating system or of the actual corrupted OS windows server 2008 in system??
i also used mant commands like sfc /scannow , run some files in recovery/bootrec...and all
please suggest me to find out the versions of corrupt windows server.and how to repair my OS...i cant afford to do fresh installation.
thanks in advance.
- Changed type seeker1234 Saturday, August 4, 2012 4:45 AM
- Changed type seeker1234 Saturday, August 4, 2012 4:46 AM
Reply:
As this discussion forum is regarding to Windows Server Backup utility and Windows Backup operation, you do not have selected a right forum for your issue. So, for better support, try to ask your question in Windows General forum at http://social.technet.microsoft.com/Forums/en-US/winservergen/threads
Please VOTE as HELPFUL if the post helps you and remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
------------------------------------
Reply:
Hi,
How are things going?
Best regards,
------------------------------------
Migrating MDS 2008 to MDS 2012-Business rules Pending
Hi,
I have migrated MDS from 2008 to 2012.I'm having issues with business rules saying pending approval.When I publish them an erro comes up saying:'Database error ocurred.Please contact your database administrator'.
Any idea how to fix this?
- Changed type Ed Price - MSFTMicrosoft employee Monday, January 19, 2015 7:45 AM
web cam download
- Changed type Jeremy_Wu Monday, September 3, 2012 9:34 AM
Reply:
Hi,
Please kindly avoid duplicate, let's focus on the same thread.
Thanks for your understanding.
Jeremy Wu
TechNet Community Support
------------------------------------
how to hide an icon from notification taskbar?
hi
i want to hode/remove scheduler idm icon but this option is not on idm or not in windows settings,
How to Update Discussion Board list programatically
i have created one discussion board list
i have a drop down list inside repeater....on select of this item from drop down list the item in column of the list should be updated ........
Reply:
As per my understanding you have to update one column in sharepoint discussionboard list.For that you need to work as usual as you update normal item in list.There is nothing extra.
http://www.sharepointkings.com/2008/09/creating-discussion-list.html
In the above link they have shown how you can new discussion in the discussionlist and then after that they had updated the value of the columns like body.You can do the same .Instead of creating you get the item and update the field.
------------------------------------
No comments:
Post a Comment